🐛 tenancy/workspace-deletion: try harder with the admin client to delete the LogicalCluster

[sttts]

Summary

The front-proxy might return errors when looking for the LogicalCluster on workspace deletion,
especially when the LogicalCluster is already gone, and it returns a 403. This PR adds another attempt through the workspace admin client.

Related issue(s)

Fixes #

Release Notes

Make workspace deletion more reliable, trying harder to not leak `LogicalClusters`.

[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 ask for approval from sttts. 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

[kcp-ci-bot]

@sttts: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kcp-verify	1d1551e	link	true	/test pull-kcp-verify
pull-kcp-verify-codegen	1d1551e	link	true	/test pull-kcp-verify-codegen

Full PR test history

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. I understand the commands that are listed here.

[yastij]

/lgtm

[kcp-ci-bot]

@yastij: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.