callback warnings/deprecations with ansible-core 2.12+

[evgeni]

With the ansible packaging re-shuffling, we now have a plain ansible-core in EL 8.6+ and should try to be compatible with that.

While running in such a setup, I've seen the following warnings:

• [DEPRECATION WARNING]: [defaults]callback_whitelist option, normalizing names to new standard, use callbacks_enabled instead. This feature will be removed from ansible-core in version 2.15.
• [WARNING]: Skipping callback plugin 'profile_tasks', unable to load
• [WARNING]: Failure using method (v2_runner_on_failed) in callback plugin (<ansible.plugins.callback.human_log.CallbackModule object at 0x7f3b291123d0>): name 'unicode' is not defined

The deprecation warning is harmless for now.

The profile_tasks callback has been moved to the ansible.posix collection which isn't available by default to core users. We don't strictly need it, but it also doesn't hurt as Ansible just ignores the setting.

The human_log callback is the one we ship in callback_plugins and that's just plain incompatible with Python 3. Again, no functional problem as Ansible is smart enough to ignore it. The normal guideline is to just replace human_log with debug as that has all the same output and was part of Ansible since 2.2, but that's also only in the ansible.posix collection and thus not available if you have core only. Annoyingly, we can't just configure the debug callback for users who have it, as there is no fallback for the stdout_callback setting and Ansible errors out: ERROR! Invalid callback for stdout specified: debug

[evgeni]

• The deprecation warning was fixed in aaea136512c76d04011f4cae2385c905286e9917
• The human_log issue is being addressed in #436 by dropping the callback
• IMHO we can also drop the profile_tasks one, as that is not available by default anyway

@ehelms @ekohl thoughts?

[evgeni]

The later is now fixed via https://github.com/RedHatSatellite/satellite-clone/pull/437

I consider this issue fixed