As a consumer of the internal support/testing endpoints of swatch, I'd like the internal API paths to be consistent and predictable, so that I can easily use them.

For each of:

• swatch-metrics done as part of SWATCH-1806
• swatch-producer-red-hat-marketplace
• swatch-subscription-sync
• swatch-system-conduit
• swatch-tally

Modify the internal API spec so that the paths consistently start with /api/$clowdapp (e.g. /api/swatch-metrics); you can use swatch-contracts and swatch-producer-aws as examples.

In order to allow the existing turnpike URLs to continue to function, create MRs for stage and prod that update the existing routes for port 8000 to rewrite the URL from /api/rhsm-subscriptions to /api/$clowdapp. For example:

- name: rhsm-metrics-internal
  route: /app/rhsm-metrics/internal/api/rhsm-subscriptions/
  origin: http://swatch-metrics-service.rhsm-prod.svc.cluster.local:8000/api/swatch-metrics/

The MRs should land at the same time as the code changes