Adjust developer scripts to use quiet mode in oscal-js when implemented

[aj-stein-gsa]

This is a ...

fix - something needs to be different

This relates to ...

• the FedRAMP OSCAL Validations

User Story

As a member of the FedRAMP engineering team, to better understand the output of the oscal-cli tooling via the oscal-js library and the dev-constraint.js script to use oscal-js quiet mode and set the default setting to console.warn and console.error for local development and CI/CD with GitHub Actions. When the ACTIONS_RUNNER_DEBUG variabel is set, then everything from console.debug and "higher" for itself and how it calls into oscal-js should be logged to terminal output for when we want to review why tests fail.

Goals

• Reduce the cognitive overhead of interpreting test harness output
• Control large amounts of output in testing for when tests fail, not when they pass

Dependencies

These must be implemented, included in a release of oscal-js, and the issues resolved before this work can continue.

• If validate throws exception or error output to terminal oscal-js#25
• Quiet mode oscal-js#26

Acceptance Criteria

• All FedRAMP Documents Related to OSCAL Adoption (https://github.com/GSA/fedramp-automation) affected by the changes in this issue have been updated.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.

Other information

See referenced issues from dependency project.

[aj-stein-gsa]

Marking this as blocked until the dependency issues can be resolved.