Although we've implemented a workaround to disable retry logic in AWS, the retry logic is still active in Azure. There is a possibility that certain statuses could still be in a "retryable" state in the Status topic, including with retry_after values. As a result, we plan to remove the column and its associated Enum in the next deployment of SWATCH-3109.

Remove references to the retry_after column from the code:

• https://github.com/RedHatInsights/rhsm-subscriptions/blob/main/swatch-billable-usage/src/main/java/com/redhat/swatch/billable/usage/data/BillableUsageRemittanceEntity.java#L85
• test to update: https://github.com/RedHatInsights/rhsm-subscriptions/blob/main/swatch-billable-usage/src/test/java/com/redhat/swatch/billable/usage/services/BillableUsageStatusConsumerTest.java#L96
• iqe: https://gitlab.cee.redhat.com/insights-qe/iqe-rhsm-subscriptions-plugin/-/blob/master/iqe_rhsm_subscriptions/data/models/billable_usage_remittance.py?ref_type=heads#L25
• https://github.com/RedHatInsights/rhsm-subscriptions/blob/main/swatch-billable-usage/src/main/java/com/redhat/swatch/billable/usage/data/RemittanceStatus.java#L39

SELECT count( * ) FROM billable_usage_remittance where status='retryable' returns 0 on stage and production

SWATCH-3913 will complete removal of the database db column after this is deployed.

Acceptance Criteria

• RemittanceStatus.RETRYABLE is deleted
• references in the code are deleted