Add static 508 banner text for local dev builds and cleanup logging

[nickviola]

Return a hardcoded 508 compliance warning banner for local dev builds instead of pulling from s3 bucket. Cleanup old console.logs that were no longer needed.

🗣 Description

💭 Motivation and context

It was decided to use this solution over providing individual AWS access keys.

🧪 Testing

Make sure local .env file includes:

IS_LOCAL=1

Login to localhost as usual and you should see the banner without access keys setup. To confirm that it's using the hardcoded value, check the backend container log output to be sure that`

Using default banner for 508 warning:

is displayed.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All future TODOs are captured in issues, which are referenced
  in code comments.
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated
  to reflect the changes in this PR.
• Tests have been added and/or modified to cover the changes in this PR.
• All new and existing tests pass.

[ameliav]

LGTM