Add fapolicyd enabled check

fapolicyd check worked on with Brie. ✨

When using fapolicyd for increased security, GitLab can report that a restore was successful but repositories show as empty. src

This check helps customers to identify whether fapolicyd is responsible for why repositories are shown as empty after a GitLab restore.

---

Adding a new check

Verification steps for review

Using RedHat (or similar) as the base OS with the default settings:

1. Run the playbook
2. The report should not have a message value for this check
3. Install and enable fapolicyd
4. Run the playbook again
5. The report should have a message value for this check

Author checklist

• After opening the MR:
  • Set it to the current milestone
  • Ask the Maintainer from the Reviewer roulette suggestion for review

---

Reviewer checklist

• I followed the verification steps and confirm the functionality of the new check
• This check does only perform read operations
• This check does not output more than necessary on stdout for the check to function
• The message explains what it means when this check does not pass
• The workaround_url provides actionable information/steps for affected users
• This check is not using the Rails console/runner, or has Maintainer approval for doing so
• If this is a breaking change check:
  • It has the corresponding xx_breaking_changes tag (xx being the major release version for the change)
  • The workaround_url goes to the entry on the https://docs.gitlab.com/update/deprecations/ page
  • The ref_url goes to the deprecation issue linked from that entry
  • The title is the same as that entry
  • The version_started is equal to the announcement_milestone of the deprecation
  • The version_fixed is equal to the removal_milestone of the deprecation