Streamline and better test Metaschema pipelines

[wendellpiez]

User Story:

Metaschema pipelines starting with composition could be streamlined and tested out more comprehensively.

They should be clean with respect to

1. Namespace handling throughout
2. Comments, both inline and initial
3. Emitted outputs including at waypoints
4. Clearly usable and adaptable runtimes for maintenance and testing

Goals:

Easier maintenance of metaschema-based production over the long term.

Dependencies:

None. Specifically, this Issue should focus on the current implementations despite (because of) possible migration of metaschema infrastructure runtimes to different platforms (node JS, XProc 3 etc).

Acceptance Criteria

• All website and readme documentation affected by the changes in this issue have been updated. Changes to the 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.

[wendellpiez]

Work is now happening in a (misnamed) feature/debug branch here: https://github.com/wendellpiez/metaschema/tree/issue196-definition-pruning-enhancement

See also #199.

This Issue needs to be rewritten with achievable goals, probably split.

[wendellpiez]

This is an aspirational Issue. Close or move to XSLT M4 stack. Also depends on unit testing.

[david-waltermire]

We need to refocus and prioritize what work needs to be done on the XSLT implementation. We should close this issue in favor of new issues that focus on specification future development actions that need to be taken.