bug: kubectl kcp bind apiexport does not support . in APIExport name

[yastij]

Describe the bug

while testing binding to an APIExport in a different workspace, @fabriziopandini and I noticed that binding to an export with a . in the name is not working when using kubectl kcp bind apiexport. when applying the APIBinding resource everything works as expected

Steps To Reproduce

1. create an APIExport with a . (e.g. bar.dev) in the name in workspace foo
2. from another workspace run kubectl kcp bind apiexport root:foo:bar.dev --name bar-binding
3. you will get the following:

error: fully qualified reference to workspace where APIExport exists is required. The format is `<logical-cluster-name>:<apiexport>` or `<full>:<path>:<to>:<apiexport>`

Expected Behaviour

I would expect the bind to succeed

Additional Context

tested from the main branch

[kcp-ci-bot]

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kcp-ci-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kcp-ci-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kcp-ci-bot]

@kcp-ci-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

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/test-infra repository.