Fixes #36528 - handle integer hash keys in katello-agent actions

[jeremylenz]

What are the changes introduced in this pull request?

For some reason, args[:dispatch_histories] is ending up with integer keys, but the code was expecting string keys. This caused no sub-plans to be created for any Katello-agent bulk action.

I changed the code to handle both string and integer hash keys. After doing this, I noticed that the action would succeed on the host, but the task would still fail:

RuntimeError

Host did not respond within 20 seconds. The task has been cancelled. Is katello-agent installed and goferd running on the Host?

This was because Katello::AgentAction#plan was still expecting options[:dispatch_histories] to have string keys. I changed that to handle both string and integer as well.

Considerations taken when implementing this change?

Originally I had just changed .to_s to .to_i, but realized I don't necessarily know for sure all the code paths that create Katello::Agent::DispatchHistorys. Figured it was safer to handle both data types.

What are the testing steps for this pull request?

Set up katello-agent:

sudo foreman-installer \
--scenario katello-devel \
--katello-devel-modulestream-nodejs=14\
--foreman-proxy-content-enable-katello-agent=true

Administer > Settings > Content > Use remote execution by default > No

Enable the RH Client repo
Install katello-agent on a host

Test basic setup: Hosts > All Hosts > your host > Packages > kebab > Install packages > Install "via katello-agent"
Task should succeed.

Test bulk actions:
Hosts > Content Hosts > Select your host (you don't need more than one) > Select action > Manage Packages > type a package name > Install > via katello-agent

Before: Task fails and Dynflow console for the task shows no subplans.
After: Task succeeds with no errors. Bulk action shows sub-plans for each host.

[theforeman-bot]

Issues: #36528

[jeremylenz]

@chris1984 added comment 👍

[lfu]

Before

After

[lfu]

LGTM 👍🏻