feat: Add support for token auth in oci-sync

[Camila-B]

No description provided.

[google-oss-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from camila-b. For more information see the Kubernetes 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

[Camila-B]

/test all

[Camila-B]

/retest

[Camila-B]

/retest

[Camila-B]

/retest

[Camila-B]

/retest

[Camila-B]

/test all

[gemini-code-assist]

Code Review

This pull request introduces support for token-based authentication for OCI sources in oci-sync. The changes are well-structured and comprehensive, spanning the oci-sync binary, reconciler controllers, API definitions, CRDs, and validation logic.

Key changes include:

• Adding flUsername and flPassword flags to oci-sync to handle credentials.
• Refactoring authenticator creation into a getAuthenticator function for better testability and clarity.
• Updating RootSync and RepoSync CRDs and API types to include a token auth type and a secretRef for OCI sources.
• Implementing logic in the reconciler-manager to securely pass credentials from the specified secret to the oci-sync container via environment variables.
• Enhancing validation to ensure correct configuration of the new authentication mechanism.
• Adding thorough unit tests for the new logic and comprehensive e2e tests for both Artifact Registry (_json_key) and generic basic auth scenarios.

The code is of high quality, and the changes are well-tested. I have no concerns with this pull request.

[tiffanny29631]

Does the password needs nil check is username is set?