feat(endpoint): switch to prod endpoint

[haarchri]

Description of your changes

switch to final endpoint

Fixes #

I have:

• Read and followed Upbound's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

[village-labs-bot]

upbound/project-template #3

Change Summary:

• Updating the endpoint URL in CI workflow from private-cli.upbound.io to cli.upbound.io, suggesting a migration from a private to a public CLI endpoint

Potential Vulnerabilities:

• File: .github/workflows/ci.yaml:21
• Code: endpoint: https://cli.upbound.io
• Explanation: Moving from a private to a public endpoint could potentially expose sensitive operations if the endpoint doesn't implement proper access controls. The security implications of this change should be carefully reviewed, especially since this involves CI/CD infrastructure.

Code Smells:

• No significant code smells identified in this change.

Debug Logs:

• No debug logs present in the changes.

Unintended Consequences:

• File: .github/workflows/ci.yaml:21
• Code: endpoint: https://cli.upbound.io
• Explanation: This change could potentially break existing CI pipelines that depend on the private CLI endpoint. It's important to verify that:
  1. All required functionality is available in the public endpoint
  2. All necessary authentication mechanisms are in place
  3. Any rate limiting or quota differences between private and public endpoints are accounted for
  4. Other projects or dependencies aren't hardcoded to use the private endpoint

Risk Score: 7

This receives a relatively high risk score because:

1. It modifies core CI/CD infrastructure
2. Changes authentication endpoints
3. Could potentially impact all downstream builds and deployments
4. Represents a fundamental shift from private to public endpoint usage