Update submodule to v1.1.2 before release

[aj-stein-gsa]

Committer Notes

Do more prep work before a possible fedramp-2.0.0-oscal-1.1.2 release.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Have you added an explanation of what your changes do and why you'd like us to include them?
• If applicable, have all FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.?
• If applicable, does this PR reference the issue it addresses and explain how it addresses the issue?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

[aj-stein-gsa]

It would seem that, for this to work, we would need to completely switch up the CI/CD for an implicit dependency on a version of an upstream container Dockerfile and docker-compose.yml removed from v1.0.6 to v1.1.0 conversion. To save us the trouble, I will close out this experimental chore branch and proceed with a minor release with the 1.0.4 model. The next 3.x.x-oscal1.1.2 release can move up to new modular "FedRAMP-native" build and conversion CI/CD when we deprecate other things per #708. This work will be revisited soon.