After SWATCH-2290 and SWATCH-2291, we emit a message containing the usage status and error code to the topic "platform.rhsm-subscriptions.billable-usage.status".

When the status is failed and the error code is subscription not found, we need to also send a message to the topic "platform.rhsm-subscriptions.billable-usage.dlt", so the usage is retried on.

After suggestion from kflahert@redhat.com, since both consumers are in the same service, we can directly update the billable usage to be retried on, directly in the status consumer without going to the topic "platform.rhsm-subscriptions.billable-usage.dlt" (context: https://github.com/RedHatInsights/rhsm-subscriptions/pull/3596#discussion_r1707540241).

Acceptance Criteria

• Update the status consumer to do what the dlt consumer did
• Remove the usage of the topic "platform.rhsm-subscriptions.billable-usage.dlt" in swatch-producer-azure (configuration and code)
• Delete the dlt consumer in swatch-billable-usage
• For QE, it should not be any effects, so only regression testing is needed