* Add Pre File Fetch Sensitivity Check

- Verify user and veteran sensitivity levels are compatible.

- Add specs and supporting services needed to perform sensitivity
level checks.

* Implement Banner for Unauthorized Vet Access

* Restore Old Error Message Logic

* Gate VBMS Methods with Sensitivity Checks

Validate user access to veteran before allowing fetch of veteran
data.

* Remove Unneeded allow Directives in Spec

* Remove Unneeded Sensitivity Checks

Checks are already handled by the sensitive_record method.

* Fix Non-Forbidden Banner Styling

…le (#1667)

* Pass Sensitivity Check Feature Toggle to UI

* Restore Manifest Sensitivity Logic

* Fix User Missing for BGS Sensitivity Check

- Update the manifests_controller's refresh method to use the
  find_or_create_by_user method to find a manifest. This will
  ensure that the user is set correctly for BGS calls.

- Move SensitivityLevelCheckFailure logic to the base_controller.

* Fix Misc. Issues

- Move rescue_from for BGS errors into the API V1 controller so
  its existing standard error rescue doesn't catch this exception.

- Improve manifests_controller request spec with sensitivity check
  logic.

- Use new method to check user/veteran sensitivity compatibility
  in the V2 ApplicationController.

- This will prevent the old "use BGS error to verify access" logic
  from running.

Co-authored-by: cacevesva <109166981+cacevesva@users.noreply.github.com>

* Send Veteran Number in Restart Request

* Update Link rel Param

- Remove recently-added frontend logic for setting veteran ID in
  refresh request as it is unreliable in the way it sets the
  veteran ID.

- Update manifests_controller to set the veteran ID using the
  manifest as this is much more reliable.

- Gem now returns the JSON body of a HTTP response, so our
  response parsing code needed to be updated to handle the new
  format.

- Update the VBMS service to alert us of any API responses that
  can't be parsed so we can troubleshoot them.

- Since the SaveFilesInS3 job is spawned by another job, it does
  not have access to RequestStore[:current_user] which is needed
  for verifying veteran/user sensitivity compatibility.

- This PR also fixes several Rubocop violations in various files.

* Adjusted UI_EXPIRY_HOURS based on deploy environment

* Adjust API HOURS

- Sort output by sensitivity level.

- Display total result count for each level.

* Removed send_user feature flag, combined with use_ce_api

* Updated vbms service spec

* Updated manifest spec for uat expiration hours

* send user feature toggle combined with use_ce_api

* Combined with ce_api feature toggle

* Update failing rspecs

* Remove feature flag from method, wrapped method with all ce api calls

* wrap ce_api related sensitivity changes

* Fix failing specs, reverted to prior code outside of feature flag

* update manifest expiry hours to not change in test + non prod

* remove pry, reverted to previous test case

* If user is blank, return

* update front end error handling

* Linting

* Revert changes

* Change type_description to mapping

* Updated rspecs to handle edge case

* pass user info to ceapi

* Update specs

* update branch name

* fix rspec

* update claim_evidence_request method

* change ref to branch

* revert x86

---------

Co-authored-by: youfoundmanesh <maneshreddy.kommidi@va.gov>

* Add CE API Error Handler Class

* Update VBMSService and SensitivityChecker Classes with Error Handling

* Update VBMSService with CE API Error Handling

* Fix Bad Method Signature

* Fix More Spec Failures