INT B-21490 Office users can switch to their secondary duty locations (Review after B-21492)

[ajlusk]

B-21490

Summary

Office users are able to switch between their primary and secondary transportation office GBLOCs similar to an HQ user.

The bulk of the secondary transportation office changes were added in B-21492 and are also included in this PR.

Also includes G-Unit's B-21627 hotfix

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. Access the admin app
2. Create several office users of various roles each with two transportation offices. At least one should be a Services Counseling Supervisor.
3. Log in as each of the users, toggle between your GBLOCs with the dropdown in the top right, switch between queues, export your queue, just try to break it.
4. As your SC Supervisor verify the origin location dropdown filter's options update with the selected GBLOC.

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

[ajlusk]

Too many failures for it to be flaky, putting it back as draft temporarily.

[antgmann]

Looks good, testing steps work nicely