Swagger documentation for facilities-api v2

[jilladams]

IN https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18314 we identified that after deprecating facilities-api V1 (correlated with Lighthouse V0), Swagger docs may need attention:

https://department-of-veterans-affairs.github.io/va-digital-services-platform-docs/api-reference/#/facilities

• Search by https://dev-api.va.gov/v0/apidocs: Facilities shows an empty header now
• Search by https://dev-api.va.gov/v1/apidocs: Facilities shows v1 endpoints for the legacy API client.
• Search by https://dev-api.va.gov/v2/apidocs: errors, not available

Which means our v2 endpoints for the facilities-api that we use aren't findable in swagger.

Related but not in scope

v1/facilities/va is still present in Swagger docs. This is the Legacy Facilities API Client and ownership is getting sorted via #18351 . Work on this situation isn't in scope in this ticket.

Acceptance criteria

• [ ] facilities_api/v2/va is available in Swagger documentation

[jilladams]

Corrections:

• Swagger docs for our V2 do exist: https://dev-api.va.gov/facilities_api/v2/apidocs
• when Mobile iterated the legacy API client/library, no docs were added

Assuming that mobile team migrates onto our facilities-api:

• The work would become deprecating Swagger for those...endpoints?

This can sit just in the backlog til ownership / migration of the legacy API client is decided.