fix: move to new org

[degenaro]

github.com/IBM -> github.com/oscal-compass
ibm.github.io -> oscal-compass.github.io

Types of changes

• Hot fix (emergency fix and release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (change which affects the documentation site)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release (develop -> main)

Quality assurance (all should be covered).

• My code follows the code style of this project.
• Documentation for my change is up to date?
• My PR meets testing requirements.
• All new and existing tests passed.
• All commits are signed-off.

Summary

Changes commensurate with new org.

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[degenaro]

Closes #1482

[AleJo2995]

@vikas-agarwal76 I have address the change you requested plus few other I found that were not addressed yet.

[AleJo2995]

LGTM. I have address Vikas's comments on @degenaro behalf plus added a couple of other misses

[georgalis]

best I can tell, org-name = and org-remarks = in docs/cli.md also needs update.
the impetus of this change set doesn't appear anywhere, either?

[vikas-agarwal76]

LGTM
@AleJo2995 Pls. go ahead and merge into develop.