Update HPP-wffc manifest URL

[Davo911]

What this PR does / why we need it:
When running cluster-sync on with external provider I was getting:

KUBEVIRT_PROVIDER=external KUBEVIRT_STORAGE=hpp make cluster-sync
+ _kubectl apply -f https://github.com/kubevirt/hostpath-provisioner-operator/releases/download/v0.24.0/storageclass-wffc.yaml
+ kubectl apply -f https://github.com/kubevirt/hostpath-provisioner-operator/releases/download/v0.24.0/storageclass-wffc.yaml
error: unable to read URL "https://github.com/kubevirt/hostpath-provisioner-operator/releases/download/v0.24.0/storageclass-wffc.yaml", server reported 404 Not Found, status code=404
make: *** [Makefile:177: cluster-sync-test-infra] Error 1

They just changed storageclass-wffc.yaml to storageclass-wffc-legacy.yaml

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:

Release note:

NONE

[akalenyu]

Thank you! we could probably just use the CSI version
(check non external provider hpp)

[Davo911]

Updated to csi, thanks @awels and @akalenyu

[awels]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [awels]

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

[akalenyu]

/override pull-containerized-data-importer-e2e-hpp-previous
ci issue

[kubevirt-bot]

@akalenyu: Overrode contexts on behalf of akalenyu: pull-containerized-data-importer-e2e-hpp-previous

Details

In response to this:

/override pull-containerized-data-importer-e2e-hpp-previous
ci issue

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.