Add host override capability to aid in tunnel scenarios

[xrstf]

Summary

Sometimes the agent might get access to kcp through tunneling or other advanced routing network magic. In this case, the URL in its kubeconfig might point to localhost on a random port. However when the agent then watches an APIExportEndpointSlice and tries to connect to it, it would only have the kcp-provided URLs for the VW endpoints. URLs which might not be directly accessible.

This PR adds a new CLI flag, --apiexport-hostport-override, which allows to configure multiple host overrides that are applied to the URLs in the APIExportEndpointSlice status. For example ./api-syncagent --apiexport-hostport-override "example.com=localhost:8445 would rewrite all virtual workspace endpoint URLs from example.com to localhost:8445. I chose to allow multiple overrides so that in complex deployment scenarios where you deploy many agents, you don't necessarily need to figure out which override is relevant to which agent, but can just give all agents the same flags, and they will use whatever matches.

What Type of PR Is This?

/kind feature

Related Issue(s)

Fixes #146

Release Notes

Add `--apiexport-hostport-override` flag to override hostnames in APIExportEndpointSlices

[kcp-ci-bot]

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

[kcp-ci-bot]

[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 assign xrstf for approval. For more information see the Code Review Process.

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

Details

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

[kcp-ci-bot]

PR needs rebase.

Details

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.