[TASK] Update or remove out-of-date cleanup script

[james-munson]

What's the task? Please describe

longhorn/scripts/cleanup.sh is out of date with respect to the resources that make up a Longhorn installation.

A clear and concise description of what the task is.
Either

• Bring it up to date, including changes to the resource list and also ability to deal with pending finalizers
  Or
• Remove it from the repo.

Describe the items of the task (DoD, definition of done) you'd like

Please use a task list for items on a separate line with a clickable checkbox https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists

• item 1

Additional context

Add any other context or screenshots about the task request here.

[innobead]

@james-munson Please help update zenhub pipeline correctly. If having any questions, consult with @PhanLe1010 or @ejweber .

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  There are none.

• Is there a workaround for the issue? If so, where is it documented?
  There is no workaround needed, since the only change is to remove a script that clearly is not in use anywhere.

• Does the PR include the explanation for the fix or the feature?

• Does the PR include deployment change (YAML/Chart)? No. If so, where are the PRs for both YAML file and Chart?
  The PR for the YAML change is at:
  The PR for the chart change is at:

• Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?

• Which areas/issues this PR might have potential impacts on?
  Area
  Issues

• If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
  Not required.

• If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
  Not needed.

• If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
  Not required (except possibly backport).

• If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
  Not required.

• If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
  Not required.

• If labeled: require/manual-test-plan Has the manual test plan been documented?
  Not required.

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at

[james-munson]

How does this ticket get tested and closed?

[PhanLe1010]

cc @khushboo-rancher

In this case, there is no testing needed. Maybe QA just directly close it?

[khushboo-rancher]

Thanks @james-munson @PhanLe1010