Remove BGS-ext services from healthchecks

[mchristiansonVA]

Summary

• This work is behind a feature toggle (flipper): NO
• Removes BGS-ext code from healthchecks

Related issue(s)

API-41368

Testing done

• New code is covered by unit tests
• During execution of v1 upstream healthchecks (called via http://localhost:3000/services/claims/v1/upstream_healthcheck for local testing), confirmed BGS-ext related healthchecks are no longer executed and related output not present in results.

Output example

{"default":{"message":"Application is running","success":true,"time":3.00002284348011e-06},"database":{"message":"Schema version: 20241108144805","success":true,"time":0.08352900005411357},"mpi":{"message":"MPI is running","success":true,"time":1.0000017937272787e-05},"localbgs-claimant":{"message":"Faraday BGS ClaimantServiceBean/ClaimantWebService is unavailable","success":false,"time":0.07229700003517792},"localbgs-corporate_update":{"message":"Faraday BGS CorporateUpdateServiceBean/CorporateUpdateWebService is unavailable","success":false,"time":0.07226400001673028},"localbgs-person":{"message":"Faraday BGS PersonWebServiceBean/PersonWebService is unavailable","success":false,"time":0.07220300001790747},"localbgs-org":{"message":"Faraday BGS OrgWebServiceBean/OrgWebService is unavailable","success":false,"time":0.07211099995765835},"localbgs-ebenefitsbenftclaim":{"message":"Faraday BGS EBenefitsBnftClaimStatusWebServiceBean/EBenefitsBnftClaimStatusWebService is unavailable","success":false,"time":0.07202100002905354},"localbgs-intenttofile":{"message":"Faraday BGS IntentToFileWebServiceBean/IntentToFileWebService is unavailable","success":false,"time":0.07186600001296028},"localbgs-trackeditem":{"message":"Faraday BGS TrackedItemService/TrackedItemService is unavailable","success":false,"time":0.07183500000974163},"benefits-documents":{"message":"Benefits Documents V1 is running","success":true,"time":0.5410760000231676},"form-526-docker-container":{"message":"Form 526 Docker Container is unavailable","success":false,"time":0.06278199999360368},"pdf-generator":{"message":"PDF Generator is unavailable","success":false,"time":0.055619999999180436}}

What areas of the site does it impact?

modules/claims_api/config/initializers/okcomputer.rb
modules/claims_api/spec/requests/metadata_spec.rb

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

Requested Feedback

I added CorporateUpdateWebService (ref PR) but wondering if we should add all of the other services created to replace BGS-ext services at this point?