[59706] Improve BGS validation error logging

[data-doge]

Summary

BGS sometimes returns errors containing an enormous stacktrace with an oracle error. This PR logs the oracle error message and excludes everything else. These oracle errors start with the signature ORA- and are bookended by a prepstmnt clause. See spec/fixtures/bgs/bgs_oracle_error.txt for an example. We want to log these errors separately because the original error message is so long that it obscures its only relevant information and actually breaks Sentry's UI.

Related issue(s)

• 686c | Improve BGS validation error logging. va.gov-team#59706

Testing done

• Added unit tests
• After deploy, I will monitor the logs on production to confirm that these logs are working as intended.

Screenshots

N/A

What areas of the site does it impact?

Form 686c

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 or Grafana (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

Requested Feedback

[ryan-mcneil]

👌