Don't build container for XSpec testing for fork-based PRs

[aj-stein-nist]

Committer Notes

As it stands, since we are evaluating using the Docker Hub registry that is not public to facilitate NIST Team development to be more efficient for local and remote testing. As this container may not exist at first commit of branch, disable on fork-based PRs for now.

Material to #1814 but does not close it.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• 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?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

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 OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.

[nikitawootten-nist]

So to be pedantic, the image isn't actually being built (due to current issues with the image see #1814) but rather pulled from a currently private registry. I think this is a good stopgap but I hope with the improvements coming in #1814 forks can opt for the "build on the fly" variant as needed.

[aj-stein-nist]

So to be pedantic, the image isn't actually being built (due to current issues with the image see #1814) but rather pulled from a currently private registry. I think this is a good stopgap but I hope with the improvements coming in #1814 forks can opt for the "build on the fly" variant as needed.

That's fair, sorry. I thought it will attempt to build and push to the registry as needed with the shell script though depending on the branch and existing cached version, am I mistaken?