usage: update example path

[sebrandon1]

Updating the repo to point to ComplianceAsCode github organization instead of the old openshift organization. I didn't touch links that went back to the old issues/ and pulls/ from the other repo.

Repository Reference Updates:

• Updated repository paths in build/Dockerfile and Dockerfile.ci to point to ComplianceAsCode/compliance-operator instead of openshift/compliance-operator. [1] [2] [3]

• Adjusted URLs in documentation files (doc/e2e-tests.md, doc/tutorials/README.md, doc/tutorials/workshop/content/index.md, doc/usage.md) to reflect the new repository location. These changes ensure that links to resources such as CRDs, installation guides, and stargazers are accurate. [1] [2] [3] [4] [5]

• Updated links in the CHANGELOG.md file to reflect the new repository URL for Helm chart deployment and release notes documentation. [1] [2]

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sebrandon1
Once this PR has been reviewed and has the lgtm label, please assign bhargavigudi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @sebrandon1. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.