Bug 2120978

.Scans and remediations correctly ignore SCAP Audit rules Audit key Previously, Audit watch rules that were defined without an Audit key (`-k` or `-F` key) encountered the following problems: * The rules were marked as non-compliant even if other parts of the rule were correct. * Bash remediation fixed the path and permissions of the watch rule, but it did not add the Audit key correctly. * Remediation sometimes did not fix the missing key, returning an `error` instead of a `fixed` value. This affected the following rules: * `audit_rules_login_events` * `audit_rules_login_events_faillock` * `audit_rules_login_events_lastlog` * `audit_rules_login_events_tallylog` * `audit_rules_usergroup_modification` * `audit_rules_usergroup_modification_group` * `audit_rules_usergroup_modification_gshadow` * `audit_rules_usergroup_modification_opasswd` * `audit_rules_usergroup_modification_passwd` * `audit_rules_usergroup_modification_shadow` * `audit_rules_time_watch_localtime` * `audit_rules_mac_modification` * `audit_rules_networkconfig_modification` * `audit_rules_sysadmin_actions` * `audit_rules_session_events` * `audit_rules_sudoers` * `audit_rules_sudoers_d` With this update, the Audit key has been removed from checks and from Bash and Ansible remediations. As a result, inconsistencies caused by the key field during checking and remediating no longer occur, and auditors can choose these keys arbitrarily to make searching Audit logs easier.