Int b 19884 authenticate non cac user

B-19884

Summary

This pull request adds the functionality for the services counselor to designate whether a customer is a cac-user or not in the edit customer info form. This will help allow a customer to login to to MilMove their first time without needing to authenticate with a CAC.

This PR does the following:

• Updated CustomerContactInfoForm to include the Cac Validation button
• Added cacUser to body for sending to backend
• Made tests for validating proper functionality of button in form.

Verification Steps for the Author

These are to be checked by the author.

• [v] Tested in the local environment
• [v] Have the Agility acceptance criteria been met for this change?

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?

How to test

1. Run server and client and login as a services counselor
2. Search for a customer and choose one then head to the edit customer info form
3. select either yes or no on the form and submit and validate the value has been updated in the database.
4. On the client side create a new user, then on services counselor side find the user and update the cacuser value to either yes or no. If value updated to yes validate user has to sign in using cac, otherwise validate they o

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.

Screenshots