B 21489 Update schema to accommodate multiple transportation offices

[r-mettler]

B-21489

INT PR

Summary

This story is part of a series of backlogs to add the ability for an Office user to have multiple Transportation Offices assigned to them. We do this by adding a new DB table populated with the current Office Users list of Transportation Offices and setting a Primary Office flag to true.

Verification Steps for the Author

These are to be checked by the author.

• Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
• Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers

These are to be checked by a reviewer.

• Has the branch been pulled in and checked out?
• Have the BL acceptance criteria been met for this change?
• Was the CircleCI build successful?
• Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

• Instructions for starting storybook
• Instructions for starting the MilMove application
• Instructions for running tests

How to test

1. Run the DB migration file
2. Open the DB and verify a new transportation_office_assignments table has been created and has all office_users and their appropriate transportation_id with the primary_office flag set to true for all of them.

Frontend

• There are no aXe warnings for UI.
• This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
• There are no new console errors in the browser devtools.
• There are no new console errors in the test output.
• If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
• This change meets the standards for Section 508 compliance.

Backend

• Code follows the guidelines for Logging.
• The requirements listed in Querying the Database Safely have been satisfied.

Database

Any new migrations/schema changes:

• Follows our guidelines for Zero-Downtime Deploys.
• Have been communicated to #g-database.
• Secure migrations have been tested following the instructions in our docs.

Screenshots

[CoryKleinjanCACI]

Matches INT.

In order to test migrations properly, I had to populate the database prior to running the migration file. Looks like everything populates properly.

[WeatherfordAaron]

lgtm