When sending messages to the topic "platform.rhsm-subscriptions.billable-usage-hourly-aggregate", for example:

BillableUsageAggregate(totalValue=1.0, windowTimestamp=2024-09-25T23:00Z, aggregateId=8ac4c79d-698d-432a-aed0-8daef71ed6e8, aggregateKey=BillableUsageAggregateKey(orgId=13259775, productId=rhel-for-x86-els-payg, metricId=VCPUS, sla=Premium, usage=Production, billingProvider=*aws*, billingAccountId=746157280291), snapshotDates=[2024-09-25T23:34:23.082387208Z, 2024-09-25T23:00:11.997578713Z], status=null, errorCode=null, billedOn=null, remittanceUuids=[b2692279-6e76-4f80-8cf4-4137cd4b5a1b])

This message is unnecessarily handled by the swatch producer aws and also the swatch producer azure because both consumers use the same group id.

I asked the Quarkus community for sending messages using Kafka Streams with a different group ID: https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/Setting.20Group.20Id.20in.20Kafka.20Streams/near/473040449 since this seems to be another limitation of the Kafka streams (other limitation is the lack of propagation of the trace id headers).

For now, the Quarkus community has said that they only support Kafka streams as best effort.

Acceptance Criteria

• One message with billing provider aws should only be handled by the swatch producer aws service, and the same with azure.