Delete collection all or single repo

[MilanPospisil]

Issue: https://issues.redhat.com/browse/AAH-2261

Depends on ansible/galaxykit#93

This PR Adds:

• Delete collection from repository - this is added into all collection menus (collection list, namespace collection list and collection detail).

• Delete collection version from repository - this is added into collection detail only.

• Both deletes from repository are only visible in standalone, since Insights mode does not have any repo management, this operation is meaningless.

• Added tests for those operations.

• existing "should copy collection version to validated repository" test is fixed

• Delete entire collection menu item name slightly renamed from "Delete entire collection" to "Delete entire collection from system" to better distinguish from "Delete collection from repository"

• deleteNamespacesAndCollections test command slightly changed. Now it does not removes orphan collections (otherwise it fails on them) and does not removes namespaces that has orphan collections. Also task wait all is used instead of more complicated waiting.

[himdel]

We should check the display_repositories feature flag for these as well (and then may not need the standalone mode checks).

[himdel]

Looks good, just the linter fix please :)

[patchback]

Backport to stable-4.7: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply c09590f on top of patchback/backports/stable-4.7/c09590f3cc5e0b787a9739d7646254e78316349b/pr-3759

Backporting merged PR #3759 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-hub-ui.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-4.7/c09590f3cc5e0b787a9739d7646254e78316349b/pr-3759 upstream/stable-4.7

4. Now, cherry-pick PR Delete collection all or single repo #3759 contents into that branch:

   $ git cherry-pick -x c09590f3cc5e0b787a9739d7646254e78316349b

   If it'll yell at you with something like fatal: Commit c09590f3cc5e0b787a9739d7646254e78316349b is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x c09590f3cc5e0b787a9739d7646254e78316349b

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Delete collection all or single repo #3759 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4.7/c09590f3cc5e0b787a9739d7646254e78316349b/pr-3759

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.