#1897 - database migration to change VAProfile and Participant IDs to big integers

[MackHalliday]

Description

issue #1897

• Update participant_id and va_profile_id from Int to BigInt to avoid NumericValueOutOfRange error when updating VA Profile ID with a given Participant ID in the MPI lookup lambda
• Downgrade will delete rows with va_profile_id values that cannnot be converted back to Int from BigInt
• Downgrade will update participant_id to (-1) if the participant_id cannot be convert back to Int to BigInt
• Updated docs regarding downgrades

Type of change

Please check the relevant option(s).

• Bug fix (non-breaking change which fixes an issue)
• Hotfix (quick fix for an urgent bug or issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Documentation changes only

How Has This Been Tested?

Test Upgrade

• Able to deploy successfully to DEV and migrations run as expected during test setup
• Able to process records with participant_id that used to throw errors

Tested Downgrade

• See Github Action here
• Tested with @kalbfled. We added two rows on the VAProfileLocalCache table - one row with a participant_id of 9223372036854775800 and another with a va_profile_id of 9223372036854775800.
  Then we ran downgrade. The participant_id row was updated to -1 and the va_profile_id row was deleted.

Checklist

• I have assigned myself to this PR
• PR has an appropriate title: #9999 - What the thing does
• PR has a detailed description, including links to specific documentation
• I have added the appropriate labels to the PR.
• I did not remove any parts of the template, such as checkboxes even if they are not used
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to any documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works. Testing guidelines
• I have ensured the latest master is merged into my branch and all checks are green prior to review
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• The ticket is now moved into the DEV test column
• I have added a bullet for this work to the Engineering Key Wins slide for review

[cris-oddball]

please test the migration downgrade and indicate this was tested in the PR's description.