INT - V2 - B - 21423 prime int sit service item

[MInthavongsay]

B-21423

Summary

This PR is a follow up to INT PR. It fixes a validation bug to prevent international SITs to be created for domestic shipments and vice versa.

This PR adds functionality to create international SIT service items to Prime (v1). In addition, it also contains the ability to update international SITs and the display of detailed information of SITs on the TOO details view. There are no BLs to address updates and display.

this article explains more about the approach used.

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. Login as customer. Create and submit HHG with Alaska origin and/or destination addresses.
2. Login as new service counselor. Click Move Details.
3. Login as TOO. Select HHG and select approve.
4. Login as Prime Sim. Find move code and click .
5. Attempt to create (domestic) origin/destination SIT. An error message displays indicating domestic SIT can not be created for international shipment.
6. Repeat step 1 and create a CONUS shipment and veriy steps 2-5.

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]

Does what it claims to do

Merged integration to get a fix for something that was breaking make db_dev_fresh.

Currently failing test is a timeout, not a normal failure.

[CoryKleinjanCACI]

No files changed after merging INT.

[MInthavongsay]

Will close out without merge. Changeset for this PR was absorbed into #14802.