Clarification in describe_module_disable macro

[Arden97]

Description:

Adding some clarifications about using install {module} /bin/false and install {module} /bin/true in remediation scripts for disabling kernel modules.

Rationale:

Changes were made in response to a RHEL-106814 ticket on Jira.

Review Hints:

• Shared macro describe_module_disable in /shared/macros/01-general.jinja file was modified. These changes will affect all of the rules that are using kernel_module_disabled template

[openshift-ci]

Hi @Arden97. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jan-cerny]

The fail of Automatus jobs is caused by running the kernel modules test scenarios as identified by CTF on a container back end which doesn't contain any kernel. The fail isn't caused by the contents of this PR. I have verified that this change updated the description in kernel_module_usb-storage_disabled.