Port Metering API and kafka listener to quarkus

• Port PrometheusMetricsTaskManager to smallrye-reactive-messaging-kafka
  • Copy PrometheusAccountSource to swatch-metrics.
• copy src/main/spec/internal-metering-api-spec.yaml to swatch-metrics/src/main/resources/META-INF/openapi.yaml
• adjust paths to /api/swatch-metrics/internal
• Needs turnpike updates to be applied during rollout
  • already done by Kevin F.

• copy InternalMeteringResource and adjust as needed
• Copy SpanGenerator to swatch-metrics
• Copy MeteringEventFactory to swatch-metrics
• Split the integration test into two, keep the event production testing in swatch-metrics and the other half (tally) in the monolith.

QE: will need to adjust api paths for metering operations accordingly ^ - this should be coordinated with stage release in SWATCH-1806. (Applied to a branch and not yet applied to the main QE tools branch).

Testing:

• /usr/bin/curl --fail -H "Origin: https://swatch-metrics-service.redhat.com" -H "x-rh-swatch-psk: ${SWATCH_SELF_PSK}" -X PUT "http://swatch-metrics-service:8000/api/rhsm-subscriptions/v1/internal/metering/sync should cause kafka messages to be produced for org with active OpenShift, etc PAYG instances (as reported by observatorium - telemeter) and events should be captured from Prometheus (metering works as usual).
• /usr/bin/curl --fail -H "Origin: https://swatch-metrics-rhel-service.redhat.com" -H "x-rh-swatch-psk: ${SWATCH_SELF_PSK}" -X PUT "http://swatch-metrics-rhel-service:8000/api/rhsm-subscriptions/v1/internal/metering/sync should cause kafka messages to be produced for org with active RHEL PAYG instances (as reported by observatorium - rhel) and events should be captured from Prometheus (metering works as usual).