Metapath array support and general maintenance

[david-waltermire]

Committer Notes

This PR adds the following new features:

• A slight improvement to the release build allowing conditional deployment of web and maven artifacts with workflow_dispatch.
• Added support for namespace qualified names, which are now used for functions, definitions, and definition references. Cleaned up namespace handling throughout. This is a foundation for supporting models that reference models in other namespaces for XML use cases.
• Completed basic support for Metapath arrays
  • Support for array construction.
  • Implemented array postfix and unary lookups.
  • Added support for the following Metapath functions:
    • array:get
    • array:put
    • array:append
    • array:subarray
    • array:remove
    • array:insert-before
    • array:join
    • array:head
    • array:tail
    • array:reverse
    • array:flatten
• Added the 'metaschema-cli metapath list-functions' command to list supported functions.
• Fixed Profile resolution subcommand returns no error with invalid JSON and YAML profiles oscal-cli#216 by ensuring that the document node returns the root node when getValue is called.

This PR also completes the following maintenance tasks:

• Normalized line endings which were inconsistent around use of lf vs crlf. Added a .gitattributes to help with this in the future. This should result in a more consistent experience on non-Windows platforms.
• Cleaned up ISequence implementations, moving getFirstItem to be a method member. Added a utility function to convert a sequence into an array member.
• Added a better means to collect the metaschema-related CLI commands for reuse.
• Fixed spotbugs issues
• Cleaned up some Javadocs.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• 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]
• Do all automated CI/CD checks pass?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you included examples of how to use your new feature(s)?
• Have you updated all website](https://pages.nist.gov/metaschema) and readme documentation affected by the changes you made? Changes to the website can be made in the website/content directory of your branch.

[david-waltermire]

This should be merged using "rebase and merge" to avoid merge conflicts in downstreams.