removed claims service and configuration files

[cadibemma]

Summary

• All VA.gov apis can share credentials. This PR removes unused code that used these separate credentials in mobile claims

Related issue(s)

• Remove unused Mobile Claims service code va-mobile-app#5732

Testing done

• None

What areas of the site does it impact?

• None

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

[kpethtel]

@aherzberg Should this ticket also include removal of the keys from the config file? What about all of the key related changes in the devops and manifest repos?

[aherzberg]

@kpethtel Im hesitant to remove stuff from the devops and manifests so soon on the off chance LH changes their mind again or if we end up integrating with some other LH CCG endpoint in the future (we could just ask LH to change the permissions allowed that key) that we are the only ones integrating with. It may not be best practice to leave code unused there but it's such a hassle to put in and remove, I don't want to do it again.

[aherzberg]

LGTM. I could go either way on removing the key from the config file within vets-api. If we keep whats in devops and manifests, may want to be consistent and keep it here too. but either way, much easier to remove and put in.

[kpethtel]

I think what @aherzberg is saying makes sense. We should probably just put another ticket in our backlog to remove those keys later.