Moving CloudWatch logging to User-Data

[cthulhuplus]

Resolves # 4020

Description

Moving CloudWatch back to user-data. If put into Packer, we'd need a separate Staging AMI since environment settings would be applied at AMI creation.

Signifcant changes or possible side effects

Automated test cases written

Steps to manually verify this change

This pull request is ready to review when

• Automated tests are updated (and all tests are passing)
• Pull request has been labeled, if applicable with feature, content, bug, tests, refactor
• Associated OpenAPI documentation has been updated
• The experience passes a basic manual accessibility audit (keyboard nav, screenreader, text scaling) OR an exemption is documented

This pull request can be merged when

• Code has been reviewed by someone other than the original author
• QA has verified the accessibility and functionality related to the change
• Design has approved the experience
• Product has approved the experience

[codecov-commenter]

Codecov Report

Merging #4148 (a9ca584) into main (4baa84d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #4148   +/-   ##
=======================================
  Coverage   87.63%   87.63%           
=======================================
  Files         215      215           
  Lines        4925     4925           
  Branches     1259     1259           
=======================================
  Hits         4316     4316           
  Misses        556      556           
  Partials       53       53           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4baa84d...a9ca584. Read the comment docs.

[cms-eapd-bot]

This deploy was cleaned up.