Revert "remove legacycloudproviders from staging"

[carlory]

This reverts commit 07c8d35.

What type of PR is this?

/kind bug
/kind failing-test
/kind regression

What this PR does / why we need it:

The publishing bot doesn't support to remove the master rule from the staging directory when the repository is being used by supported releases. so I have to revert the changes made by #124862 in order to not break the pull-publishing-bot-validate job, see #124829.

The reverted PR is expected to be merged after 1.30 goes out of support. I add a to-do item to #124771 to remind us to do so.

Which issue(s) this PR fixes:

Ref #124829
Ref #124862

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Revert "remove legacycloudproviders from staging"

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[carlory]

/hold
waiting a feedback.

[carlory]

/test pull-kubernetes-e2e-gce

[pacoxu]

/retest
/approve
/lgtm
for #124861 and kubernetes/publishing-bot#433
/assign @saschagrunert @dims

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2948e9880dac898266eb8aa21445507091a0cdaa

[k8s-ci-robot]

@carlory: The following test 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-publishing-bot-validate	d9a0be3	link	false	/test pull-publishing-bot-validate

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

[saschagrunert]

/skip

That pull-publishing-bot-validate fails is intentional since it does not exist any more.

[dims]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: carlory, dims, pacoxu, saschagrunert

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 [dims]
• hack/OWNERS [dims]
• staging/OWNERS [dims]

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

[carlory]

/hold cancel