If authselect isn't enabled, the playbook would terminate here.
In normal mode it makes sense because subsequent tasks depend on
authselect and use the authselect command. But, in check mode,
it isn't possible to enable authselect, so we need to skip this check.

Tasks using shell or command module normally don't run in check mode.
Setting the check_mode attribute to false on a task using shell or command module
will cause that this task will be executed also in check mode.
This can't be done on all these tasks but only on tasks that don't
perform any change to the system but they just read a value or
read a status of something (for example grep commands).

Check that the file modified in the tasks exists before starting
the tasks to prevent errors "no such file".

Prevent executing tasks depending on authselect profile
if authselect profile hasn't been created.

Prevent playbook termination in check mode if aide hasn't been
installed.

Prevent fails in check mode caused by attempts to modify nonexistent
files. Make sure AIDE is installed before trying to modify AIDE
configuration files.

Prevent fails in check mode caused by attempts to modify nonexistent
files. Make sure fapolicyd is installed before trying to modify fapolicyd
configuration files.

The task fail is check mode because the /etc/cron.daily/logrotate
doesn't exist. This fail can happen only in check mode because in the
normal run the file is created in the task right before.

This prevents errors in check mode. In normal mode it doesn't
have an effect because the file is created by the previous task above.

If the file doesn't exists it fails with "No such file or directory: b'gpg'"

Prevents termination in check mode if the service doesn't run
because a playbook in check mode doesn't start services, it only
checks