Revert with-parent-controls from profile schemas and update specification

[aj-stein-nist]

User Story

As an OSCAL tools developer, to ensure consistency and ease of development, I would like to have only with-child-controls in the schemas (as they are currently released) and have the specification removed to exclude with parent controls from the schemas and profile resolution specification permanently.

Goals

• Minimize burden on developers for implementing profile resolvers
• Simplify the interfaces of profile resolution where similar syntactic constructs (based on syntax name) have dissimilar behavior

Dependencies

No response

Acceptance Criteria

• Remove metaschema definition of with-parent-controls from OSCAL Profile model metaschema module
• Update specification
• Update applicable tests
• All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Revisions

No response

[aj-stein-nist]

Re the remaining AC criteria, @aj-stein-nist is going to push some changes to adapt extant profile resolution tests and functionality in develop to align with this change that was covered in #1819.