Disable AppArmor before running Molecule tests

[jsf9k]

🗣 Description

This pull request modifies the build.yml workflow to leverage cisagov/action-disable-apparmor to disable AppArmor before running the Molecule tests.

💭 Motivation and context

This is a better (less janky) solution to the AppArmor woes than #216. We are also already taxing the free GitHub runners, and I have seen failures in the steps added in #216. This solution should tax the runners a bit less.

It is also worth noting that lot of folks (me included) are of the opinion that AppArmor shouldn't be enabled in the GitHub runners.

Resolves #215.

🧪 Testing

All automated tests pass.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All new and existing tests pass.

✅ Pre-merge checklist

• Use the v1 tag of cisagov/action-disable-apparmor once First commits action-disable-apparmor#1 is approved and merged.

[mcdonnnj]