[DevOps] Remove LoROTA Cleanup Lambda and schedule.

[ndouglas]

Description

Replaces #83454.

Per this:

• https://dsva.slack.com/archives/C04G3EY2F5W/p1686543809242819
• https://dsva.slack.com/archives/C038C047X2P/p1681476474614209

the existing Cleanup Lambda is not useful and has no reason for existing, and creates some log spam each and every day.

Tasks

• [x] [DevOps] Remove references to Cleanup Lambda from CloudFormation and Terraform templates.
• [x] [DevOps] Remove Cleanup Lambda and any tests from codebase.
• [x] [DevOps] Preview CloudFormation plan; are there any other unexpected changes resulting from drift?
• [x] [DevOps] If not, apply CloudFormation changes on lower environments.
• [x] [DevOps] Consider how to move forward on production; should we just disable the cleanup lambda? Applying the CF is scary at this point. Probably discuss with Brian, John, Gaurav, and Kanchana.

Acceptance Criteria

• [ ] The Cleanup Lambda does not run in vaec-cms on any environment.
• [ ] The Cleanup Lambda does not run in vaec-cie on any environment.
• [ ] The Cleanup Lambda is removed from the codebase and IaC.

[ndouglas]

Created a dashboard here I can review to monitor whether there is an unanticipated growth in item count because of these changes.

[ndouglas]

Posted comment in Slack here [1], disabled the Amazon EventBridge rule (LoROTA_scheduled_cleanup_prod) that triggers the Lambda. Now we wait 😎

[1] https://dsva.slack.com/archives/C04G3EY2F5W/p1719414180003349

[ndouglas]

No apparent ill effects as of yet.