Deprecate legacy kube-burner workload

[rsevilla87]

Type of change

• Refactor
• New feature
• Bug fix
• Deprecation
• Documentation Update

Description

The workload's on this directory shouldn't be used anymore, people should use https://github.com/cloud-bulldozer/e2e-benchmarking/tree/master/workloads/kube-burner-ocp-wrapper going forward.

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.

[rsevilla87]

Please, feel free to tag more affected users.
cc: @mffiedler

[dry923]

@rsevilla87 Can we add an estimated removal date or something as well when the directory will be removed?

[jtaleric]

Since this change only removes the CI runs I am good with it... I do think there are teams (ACS in particular) using non-ocp-wrapper kube-burner.

[paigerube14]

Agree with Joe! Think it's ok to remove ci references. Not sure if we are fully ready (qe) side for a full removal of kube burner folder

[rsevilla87]

Agree with Joe! Think it's ok to remove ci references. Not sure if we are fully ready (qe) side for a full removal of kube burner folder

Thanks for the feedback!, as @dry923 also suggested, we should maybe add an EOL date so we can definitively remove the kube-burner directory.
I'll add October as EOL (remove) for this directory, if you agree.