Description of Problem

In the RHEL 10 (Go implementation) of rhc-worker-playbook, the process will continue to upload playbook output even after the playbook has finished executing.

Every 30 seconds (or configured interval), it will continue to upload the same (final) payload of Ansible job events until the process is killed, loses network connection, or other forced stoppage.

How reproducible

Always

Steps to Reproduce

1. Execute a playbook run on a RHEL10 system
2. Observe the output of the `com.redhat.Yggdrasil1.Worker1.rhc_worker_playbook.service` systemd unit
3. Wait until playbook status is reported to the web UI as "Success"
4. See that rhc-worker-playbook service is still continuing to upload data

Actual Behavior

rhc-worker-playbook uploads data on intervals continuously after playbook ends

Expected Behavior

rhc-worker-playbook should end its uploads when the playbook is finished

Business Impact / Additional info

Unnecessary waste of bandwidth & computation resources for both us and the customers, and goes counter to our data/bandwidth reduction efforts for remediations