Address OSCAL and Metaschema Java library defects

[david-waltermire]

User Story:

As a user of the Metaschema Java and OSCAL Java libraries, I need know defects to be repaired. I also need the OSCAL Java library to be updated to the latest OSCAL release.

Goals:

The following issues need to be addressed for the next release of the OSCAL Java library:

• Dependencies need to be updated
• Change stream autoclose behavior. See Updated to liboscal-java 1.0.2 and addressed changes EasyDynamics/oscal-rest-service#91 (comment)
  - [ ] Import/Export loop of NIST_SP-800-53_rev5_catalog.xml produces a different XML than the original liboscal-java#3
  - [ ] Invalid handling of markdown text with nested style when saving to XML liboscal-java#5
  - [ ] IllegalArgumentException when serialising Profile elements using Boolean liboscal-java#6
• Inconsistent handling of URLs in hrefs and rlinks liboscal-java#12
  • Add mechanism to allow overriding URL resolution behavior. See Add support for entity resolution of URIs passed to the loaders and validators metaschema-java#28.
  • Ensure new mechanism is used whenever a URL is resolved. See Improved URL handling in profile resolution liboscal-java#20.
    - [ ] Incorrect serialization of list items in XML liboscal-java#13
• Inconsistent quotations in serialized XML declaration liboscal-java#14
• Profile resolution incorrectly maps the oscal-version from the version on the source profile liboscal-java#15. See Correct OSCAL version handling in resolved profile liboscal-java#21.
• Profile resolution does not maintain parties and related nodes liboscal-java#17
• Custom validation violation handling liboscal-java#19

Dependencies:

None.

Acceptance Criteria

• 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.

[david-waltermire]

Issues have been resolved an will be released with the liboscal-java v1.0.4 release.