INT - B - 21423 prime int sit service item

[MInthavongsay]

B-21423

Summary

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. For Service Item Type, verify there are options for International Origin SIT and International Destination SIT.
6. Select International Origin SIT and fill out form. Click create service item. Verify 4 service SIT items are created after page redirect/refresh.
   
7. Select International Destination SIT and fill out form. Click create service item. Verify 4 service SIT items are created after page redirect/refresh.
   
8. Login TOO. Verify 2 sets of SIT service items are present to approve/reject for international origin and destination SITs. Verify details of individual are displayed correctly. Use domestic origin/destination SITs as reference. Note: There is an issue with "Delivery miles into SIT" for international SITs. This needs to be addressed in another BL.
   
9. Play around with the SITs by approving/rejecting/editing(if available). Confirm behavior should be identical to domestic SITs.
10. Log back into Prime Sim and test update for each SITs. Behavior should be the same as domestic.
11. Log back into TOO and verify updated SITs have been updated.
12. Verify Reject. Behavior should be the same as domestic.
13. Try to break it!
14. Go to swagger: http://primelocal:3000/swagger-ui/prime.html#/mtoServiceItem/createMTOServiceItem . Use Prime Sim UI to get sample JSON payload via web developer tool.
    
15. Go to swagger: http://primelocal:3000/swagger-ui/prime.html#/mtoServiceItem/updateMTOServiceItem . Use Prime Sim UI to get sample JSON payload via web developer tool. Submit and verify via UI update data is present.

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

[robot-mymove]

	Warnings
⚠️	This PR does not include changes to storybook, even though it affects component code.

Generated by 🚫 dangerJS against 86fe5c4

[danieljordan-caci]

Just some little stuff during static review, use variables where ya can for the UI

[ajlusk]

These mostly seem like copy & paste errors.

The core functionality seems to work as described and I haven't been able to break it yet other than these little things.