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
• swatch-producer-red-hat-marketplace
• swatch-subscription-sync
• swatch-system-conduit
• swatch-tally
• swatch-producer-aws

• swatch-contracts

and for both stage and prod, create a route within turnpike that is formatted as follows:

- name: $clowdapp
  route: /api/$clowdapp
  origin: http://$clowdapp-service.rhsm-$env.svc.cluster.local:8000/api/$clowdapp/

For example:

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