We need to relocate the flaky test "test_remittance_matches_tally_snapshot_data_for_non_contract_products_with_billing_factor_equal_one" into a component test.

Currently, we have an IQE test (test_remittance_matches_tally_snapshot_data_for_non_contract_products_with_billing_factor_equal_one) that validates remittance data against tally snapshots. This test runs in the IQE suite but frequently times out while waiting for Kafka messages from the billable-usage service. The timeout occurs after the test successfully verifies remittance data but fails when checking for the hourly aggregate messages on the Kafka topic.

This flakiness happens because the integration test environment has timing issues and dependencies on external services like Kafka Bridge. By moving this to a component test within the billable-usage service itself, we can control the test environment better, make it more reliable, and get faster feedback during development.

The error message shows: "The action 'wait for 1 kafka messages' was not completed within the timeout period" - indicating that while the service processes the data correctly (remittance records are created), the test infrastructure can't reliably verify the Kafka output in the integration environment.

Example link: https://ci.ext.devshift.net/job/RedHatInsights-rhsm-subscriptions-pr-check/13670/testReport/junit/tests.component.swatch_billable_usage/test_swatch_billable_usage/test_remittance_matches_tally_snapshot_data_for_non_contract_products_with_billing_factor_equal_one/

Acceptance Criteria:

• Add the component test in billable-usage service
• Delete the IQE test