VEBT 1091 - Rename vawave files to end in 3 digit numbers

[alexchan-va]

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Summary

• This work is behind a feature toggle (flipper): YES/NO no
• (Summarize the changes that have been made to the platform) Standardized the naming of the vawave file so that it always ends in 3 digits
• (If bug, how to reproduce) n/a
• (What is the solution, why is this the solution?) Change string formatting
• (Which team do you work for, does your team own the maintenance of this component?) VEBT
• (If introducing a flipper, what is the success criteria being targeted?) n/a

Related issue(s)

• Link to ticket created in va.gov-team repo OR screenshot of Jira ticket if your team uses Jira https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.devops.va.gov%2Fbrowse%2FVEBT-1091&data=05%7C02%7C%7Ce1c1323ada954fc0efb408dd3a3d21ad%7Ce95f1b23abaf45ee821db7ab251ab3bf%7C0%7C0%7C638730756403379784%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FROG532f7C8GJNRBoFFLWDlhNDagCCH9l4rVoAGlXhE%3D&reserved=0
• Link to previous change of the code/bug (if applicable) n/a
• Link to epic if not included in ticket

Testing done

• [x ] New code is covered by unit tests
• Describe what the old behavior was prior to the change It only made files without 0 padding (i.e. vawave1 vs vawave001)
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing Check S3 buckets to confirm correct naming
• If this work is behind a flipper: n/a

Screenshots

Note: Optional

What areas of the site does it impact?

(Describe what parts of the site are impacted andifcode touched other areas) none

Acceptance criteria

• [x ] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• [x ] No error nor warning in the console.
• [x ] Events are being sent to the appropriate logging solution
• [x ] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs

Requested Feedback

(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[stevenjcumming]

I've never seen this before, but that's pretty cool