CST - Added db migration to update evidence_submissions fields from type string to integer

[pmclaren19]

Summary

This pr is related to the work from #20105. As part of that work we need to update the request_id, claim_id and tracked_item_id to be integers instead of strings. Currently the table evidence_submissions is not being used and is behind the feature flag cst_send_evidence_submission_failure_emails which is currently disabled in upper environments.

This pr is currently blocking the pr here.

Related issue(s)

-Link to ticket created in va.gov-team repo department-of-veterans-affairs/va.gov-team#100037

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
• If this work is behind a flipper:
  • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
  • What is the testing plan for rolling out the feature?

What areas of the site does it impact?

Claim Status Tool

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

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]

@pmclaren19 sorry I didn't catch this sooner, but there needs to be data migration for a column type change

https://depo-platform-documentation.scrollhelp.site/developer-docs/vets-api-database-migrations#vets-apidatabasemigrations-Changingacolumntype(🐉)

[jerekshoe]

@pmclaren19 sorry I didn't catch this sooner, but there needs to be data migration for a column type change

https://depo-platform-documentation.scrollhelp.site/developer-docs/vets-api-database-migrations#vets-apidatabasemigrations-Changingacolumntype(🐉)

There isn't any data in the table currently, is there a need to worry about data migrations in that case?