Create a new message consumer in tally service to process dead letter messages from billable-usage.dlq. These messages should update the billable_usage_remittance records with a retry_after from the header.

Tally Service

• New consumer of billable-usage.dlq
  • If header exists
    • Populate retry_after column in the billable_usage_remittance table
  • Else
    • We log it as an unrecoverable failure at INFO level
    • This is where we would build out other failure strategies later

AC:

• When a billable-usage.dlt message is sent, the consumer reads the message and adds a retry_after value to the database record
• if there is no retry_after then log the failure at info level
• GET /internal/remittance/accountRemittances will now include the retry_after field. (For QE, internal_api_account_remittance() in mqe-tools hits that end point)