fix: ensure removed kernel modules are not loaded at boot; add module remediation test

[richm]

Ensure that removed/unloaded kernel modules are not reloaded at boot. It seems that
the upgrade run can reboot the system after analysis but before upgrade, and if the
unsupported kernel modules are not disabled, they will be loaded again at boot.

I have also added a test for the unsupported kernel module remediation.

This also refactors the kernel module load/unload code into a new common
tasks file manage_kernel_modules.yml which implements the modprobe plus the
module file handling.

[richm]

[citest]

[richm]

[citest]

[richm]

[citest]

[richm]

[citest]

[richm]

[citest]

[richm]

[citest]

[richm]

[citest]

[richm]

[citest]

[richm]

[citest]

[richm]

@swapdisk I don't know if we have changed something since we have been working on the role, but now during some cases the node is rebooted after analysis and before upgrade, and this causes kernel modules to be reloaded, even if they have been unloaded with the modprobe module, which causes upgrade to fail with inhibitors. I'm wondering why this ever worked? Note that the modprobe module, if you use persistent: absent, will manage the module-load and modprobe files, but only if they already exist. In this case, they do not.

[richm]

[citest]

[richm]

tests are failing because the pata_acpi module is not available on el8 or later. I have asked the leapp team for information about which modules are flagged as inhibitors that I can use for testing.

[richm]

[citest]

[richm]

It doesn't like floppy - need to revisit the list

[richm]

[citest]

[spetrosi]

lgtm except for one question

[richm]

[citest]

[richm]

if no further comments, please merge