Remove unused multi-tenancy creds

[CecileRobertMichon]

What type of PR is this?

/kind cleanup

What this PR does / why we need it: Noticed these leftover creds are no longer used anywhere and were leftover from an old test that got removed.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

• cherry-pick candidate

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

NONE

[CecileRobertMichon]

/assign @nojnhuh @mboersma

[CecileRobertMichon]

/cherry-pick release 1.10
/cherry-pick release 1.9

/test pull-cluster-api-provider-azure-e2e-optional

[k8s-infra-cherrypick-robot]

@CecileRobertMichon: once the present PR merges, I will cherry-pick it on top of release 1.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release 1.10
/cherry-pick release 1.9

/test pull-cluster-api-provider-azure-e2e-optional

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.

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +0.01% 🎉

Comparison is base (7e8c80b) 54.37% compared to head (d04bfa1) 54.38%.
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3797      +/-   ##
==========================================
+ Coverage   54.37%   54.38%   +0.01%     
==========================================
  Files         187      187              
  Lines       19015    19015              
==========================================
+ Hits        10340    10342       +2     
+ Misses       8117     8115       -2     
  Partials      558      558              

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nojnhuh]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2684454273493166ac977072f335c81b576fd0d3

[CecileRobertMichon]

/retest

[mboersma]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mboersma

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mboersma]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mboersma]

/retest

[k8s-infra-cherrypick-robot]

@CecileRobertMichon: cannot checkout release 1.10: error checking out release 1.10: exit status 1. output: error: pathspec 'release 1.10' did not match any file(s) known to git

In response to this:

/cherry-pick release 1.10
/cherry-pick release 1.9

/test pull-cluster-api-provider-azure-e2e-optional

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.

[k8s-infra-cherrypick-robot]

@CecileRobertMichon: cannot checkout release 1.9: error checking out release 1.9: exit status 1. output: error: pathspec 'release 1.9' did not match any file(s) known to git

In response to this:

/cherry-pick release 1.10
/cherry-pick release 1.9

/test pull-cluster-api-provider-azure-e2e-optional

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.

[mboersma]

/cherry-pick release-1.10
/cherry-pick release-1.9

[k8s-infra-cherrypick-robot]

@mboersma: new pull request created: #3801

In response to this:

/cherry-pick release-1.10
/cherry-pick release-1.9

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.

[mboersma]

/cherry-pick release-1.9

[k8s-infra-cherrypick-robot]

@mboersma: new pull request created: #3802

In response to this:

/cherry-pick release-1.9

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.

[CecileRobertMichon]

cannot checkout release 1.10

whoops, thank you @mboersma!