Tests: Remove AI-generated artifacts from tests

[alromeros]

What this PR does / why we need it:

This PR removes unnecessary ai-generated docs that were mistakenly included in #404.

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

[alromeros]

@weshayutin let me know if you are ok with these changes.

[weshayutin]

well.. until it's socialized that these tests were running the WRONG types of backups I would like to leave it. In the branches other than main, the tests run volumesnapshot backups and restic backups, neither are supported by velero for vm's.
The backups were also not waiting to start until the vm's were fully up, causing race conditional failures.

Now moving to CSI - supported
Now waiting for VM and Volumes to be running and bound.
Now we're testing what is actually supported.

So actually, this can be rewritten or moved but not removed entirely. That's my opinion, but I'm not in charge :)

[kubevirt-bot]

@weshayutin: changing LGTM is restricted to collaborators

Details

In response to this:

well.. yes we can remove. However until it's socialized that these tests were running the WRONG types of backups I would like to leave it. In the branches other than main, the tests run volumesnapshot backups and restic backups, neither are supported by velero for vm's.
The backups were also not waiting to start until the vm's were fully up, causing race conditional failures.

Now moving to CSI - supported
Now waiting for VM and Volumes to be running and bound.
Now we're testing what is actually supported.

So actually, this can be rewritten or moved but not removed entirely. That's my opinion, but I'm not in charge :)

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.

[weshayutin]

ya.. I need to make sure we communicate what was changed, especially to QE.

[kubevirt-bot]

@weshayutin: changing LGTM is restricted to collaborators

Details

In response to this:

ya.. I need to make sure we communicate what was changed, especially to QE.

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.

[weshayutin]

0/ approved
/LGTM

[kubevirt-bot]

@weshayutin: changing LGTM is restricted to collaborators

Details

In response to this:

0/ approved
/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-sigs/prow repository.

[alromeros]

/lgtm
/approve
Merging as discussed in #404. Thanks @weshayutin!

[kubevirt-bot]

@alromeros: you cannot LGTM your own PR.

Details

In response to this:

/lgtm
/approve
Merging as discussed in #404. Thanks @weshayutin!

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.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alromeros

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 [alromeros]

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

[awels]

/lgtm