Add E2E test for lighthouse /disabilities endpoint

[lukey-luke]

User Story

As an engineer, I want CI to fail when classification mappings for Contention Classification API(s) are no longer up-to-date, so that claims are correctly processed in downstream services like VBMS.

Acceptance Criteria

1. Ensure currently used mappings are stored in version control.
2. Daily job run to GET /disabilities
3. If the current lookup table mappings are out of date, send an alert (slack maybe?)
4. If new mappings are available, log message to CI output

Not included in this work Notes about work

• info on /disabilities can be found HERE.
• This is public reference data, anyone can generate an API key

[dianagriffin]

@verdance-luke I'll set up some time to discuss this together with some VRO engineers. A few questions coming up:

• How often do the mappings change?
• Does it have to be part of a build to update the mappings?
• Help us understand why you want failing at CI to be the point where this is alerted?

[yurenanava]

Bring in the next VRO refinement session

[dianagriffin]

@verdance-luke @yurenanava This would be a great option to put through the new VRO request intake form to provide a little more context! https://github.com/department-of-veterans-affairs/abd-vro/issues/new/choose