[L] DUP: Update AWS SDK to V3

[JLWade]

Description:

Update AWS-SDK from V2 to V3. When using V2 it is fairly common to see warnings about outdated functionality along with a reminder V2 is nearing end of support. This task is go through the process of updating to V3, resolve all the warnings, and test the app to ensure any breaking changes caused from this update have been resolved.

Amazons guide for Updating to V3

Acceptance Criteria:

Day use pass now uses AWS-SDK V3.

Development Checklist:

• [ ] all warnings about v2 to v3 have been resolved
• [ ] Maintain functionality
• [ ] API, Public, Admin now using V3

Dependencies

• Blocked by #336
• Blocking

Relevant documentation as reference

Definition of Ready

• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if applicable)
• [ ] Design / Solution is accepted by Product Owner (if applicable)
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] UI meets accessibility requirements
  • [ ] Unit tests are written
  • [ ] Work is traceable in GitHub
  • [ ] PR linked to ticket number
  • [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • [ ] Code is peer reviewed and has passed CI/CD tests
• QA:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Code is potentially shippable to the production environment
  • [ ] Functional features have been tested and passed by QA
  • [ ] UI components tested by designer
  • [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Reviewed and approved by Product Owner

Notes:

• MPORTANT: Switching to V3 will cause successful tests to fail in the GH environment. The issue has something to do with the asynchronous startup of DynamoDB. You MUST incorporate a sleep command into the on-pr test routine to WAIT for DynamoDB to be ready by the time tests run. Also use --runInBand to run tests in series to reduce the consecutive dynamodb load. Review here to see implementation

[Dianadec]

Copy info into #326 when AC added

[Dianadec]

May want to wait to do this until the SAM update is done. We'll move this to the following sprint (as per sprint planning convo)

[JLWade]

Notes from refinement May 28, 2024:

• needs to be done, but wait until SAM is done (#336 )
• V2 SDK is still good until Sept (probably)
• "wold-ending" changes coming up (ie. high priority technical debt and urgent upgrades/maintenance): SAM (need to transition off of terraform), SDK V3, AWS BC SEA to LZA zones