Profile Check Schematron Enhancements Fail in GHA Due to Relative Path Issues

[aj-stein-nist]

Describe the bug

OSCAL profile checks work some of the time after #1513 was merged into develop, but relative pathing issues with how our shell harness works with the presumed working directory is relative to the source file target of the transform. This exhibits inconsistent behavior between the docker-compose-based method, which uses a mount at "the current directory" mounted at /oscal in the container versus /github/workspace called at a different path without Docker used at all, so specific hard-coded relative paths cause errors.

This was discovered while continued worked on debugging usnistgov/oscal-content#139 to reproduce a bug, figure out, and finalize a solution for usnistgov/metaschema#235.

Who is the bug affecting

NIST OSCAL developers relying on Schematron to validate profiles, which will fail builds prematurely without Schematron validation taking place at all early in the process.

What is affected by this bug

CI/CD, Metaschema

How do we replicate this issue

1. Review commit in example oscal-content branch for debugging: usnistgov/oscal-content@c790bc0
2. Review CI/CD errors if they existed, but they have since expired. :-(

Expected behavior (i.e. solution)

Paths are handled correctly and validation completes without issue, only errors if validation errors occur and document instances need correcting.

Other comments

N/A