Description of problem:

In Satellite 6.14.2 or later, Whenever we perform some repo sync tasks, with every single poll attempt on the tasks, a lot of dynflow-related warnings are bring printed and they are flooding the logs.

Consider a scenario where some daily or weekly sync plans are configured, the syslog will be completely flooded with those dynflow warning messages.

Version-Release number of selected component (if applicable):

Satellite 6.14.2 or later
Sidekiq 6.5 or later

How reproducible:

Always

Steps to Reproduce:
1. Install Satellite 6.14.2
2. Import a manifest with one valid RHEL sub
3. Enable couple of repos and sync them
4. Check /var/log/messages file

Actual results:

Lots of dynflow warnings printed in the logs e.g.

Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: 2024-02-21T09:14:06.322Z pid=18149 tid=gq1h WARN: Job arguments to Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork do not serialize to JSON safely. This will raise an error in
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: by calling `Sidekiq.strict_args!` during Sidekiq initialization.
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: 2024-02-21T09:14:06.322Z pid=18149 tid=gq1h WARN: Job arguments to Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork do not serialize to JSON safely. This will raise an error in
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: by calling `Sidekiq.strict_args!` during Sidekiq initialization.
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: 2024-02-21T09:14:06.375Z pid=18256 tid=bdjg class=Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork jid=38083cc9eff10ddbad79dc3a WARN: Job arguments to Dynflow::Executors::Sidekiq::OrchestratorJobs::WorkerDone do not serialize to JSON safely. This will raise an error in
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: by calling `Sidekiq.strict_args!` during Sidekiq initialization.
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: 2024-02-21T09:14:06.394Z pid=18256 tid=bdtc class=Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork jid=f65b85d85d3c50c390ce14e3 WARN: Job arguments to Dynflow::Executors::Sidekiq::OrchestratorJobs::WorkerDone do not serialize to JSON safely. This will raise an error in
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: by calling `Sidekiq.strict_args!` during Sidekiq initialization.
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: 2024-02-21T09:14:06.395Z pid=18149 tid=gq1h WARN: Job arguments to Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork do not serialize to JSON safely. This will raise an error in
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
Feb 21 14:44:06 satellite614 dynflow-sidekiq@orchestrator[18149]: by calling `Sidekiq.strict_args!` during Sidekiq initialization.
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: 2024-02-21T09:14:06.673Z pid=18256 tid=bdv8 class=Dynflow::Executors::Sidekiq::WorkerJobs::PerformWork jid=048a864113a8000f63dbf5a0 WARN: Job arguments to Dynflow::Executors::Sidekiq::OrchestratorJobs::WorkerDone do not serialize to JSON safely. This will raise an error in
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today
Feb 21 14:44:06 satellite614 dynflow-sidekiq@worker-1[18256]: by calling `Sidekiq.strict_args!` during Sidekiq initialization.

Expected results:

No such warnings or error messages or an option to suppress them

Additional info:

Related github issue https://github.com/Dynflow/dynflow/issues/436