Swapped Implementation Step #2 in COMMONCONTROLS.11.4v0.1 and COMMONCONTROLS.11.5v0.1 per Issue 143

[jkaufman-mitre]

🗣 Description

In COMMONCONTROLS.11.4v0.1 and COMMONCONTROLS.11.5v0.1, the implementation step 2 was swapped. When it and put the implementation step under the correct policy.

Fixes #143

💭 Motivation and context

• This change is required to ensure that the implementation steps listed are under the correct policy identifier

🧪 Testing

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• If applicable, All future TODOs are captured in issues, which are referenced in the PR description.
• The relevant issues PR resolves are linked preferably via closing keywords.
• All relevant type-of-change labels have been added.
• I have read and agree to the CONTRIBUTING.md document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• Tests have been added and/or modified to cover the changes in this PR.
• All new and existing tests pass.

✅ Pre-merge Checklist

• This PR has been smoke tested to ensure main is in a functional state when this PR is merged.
• Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge Checklist

• Delete the branch to clean up.
• Close issues resolved by this PR if the closing keywords did not activate.

[tmcomeau]

Consider adding label for "code impact" or "non code impact" for this PR and future ones.