Api 27356 27357 docs service and logging

[FonzMP]

Summary

• Adds some generic logging and creates a bypass for failed EVSS Documents Requests. Will essentially ignore supporting docs if the service is down or responds with an error. I need to speak with VA Gov on this because it will impact how our service builds Tracked Items.
• I also expect that we'll want to move the logging to Datadog eventually, or in the near future. We have a ticket to explore and enhance logging in v2, so we can use that ticket to investigate.

Related issue(s)

• https://jira.devops.va.gov/browse/API-27356
• https://jira.devops.va.gov/browse/API-27357

Testing done

• Local testing and rspec

What areas of the site does it impact?

Claims Show V2 specifically and logging from within the inherited application controller.

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