101550: Update DR service to LH to use Common::Exceptions for API request errors

[dfong-adh]

Summary

• This work is behind a feature toggle (flipper): YES/No
  Yes. The behavior is behind the flipper flag decision_review_service_common_exceptions_enabled

Our service class DecisionReviews::V1::Service primarily returns DecisionReview::ServiceError exceptions when errors occur while making API requests to other services. This PR updates the service to use the common exception classes in Common::Exceptions for status codes instead.

Related issue(s)

department-of-veterans-affairs/va.gov-team#101550

Testing done

• New code is covered by unit tests

What areas of the site does it impact?

This impacts the Decision Review service and the format of data being logged to the PersonalInformationLog table.

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

[kayline]

Got it, approved!

[stevenjcumming]

Please update the Flipper enables in the spec to look like this

allow(Flipper).to receive(:enabled?).with(:feature_flag).and_return(false)