Improve list of resources to delete in PromptRemove

[richard-cox]

Setup

• Rancher version: 2.6.6

Describe the bug This is following on from https://github.com/rancher/dashboard/issues/6257 and the discussion in slack (~1st July).

The resource list is currently comma separated, the requirement now is to make the list bullet pointed. Consideration should be given to

• The max case where all resources from a table at max page size are deleted (currently 1000). We may wish to display these in a different way, or at least make the list nicely scrollable.
• The min case where only one resource is deleted

To Reproduce Multiple Resources

• Select multiple resource of any type to delete
• Use the bulk Delete button above the table, see the modal then shown

Single Resources

• In any resource table click on a row's action menu (three button on right) and click delete, see the modal shown

Screenshots

[Josh-Diamond]

This looks great. One idea i had, was if we make the bullet point list scrollable, maybe we should not include the Delete button in the scrollable list of clusters, but just have it fixed to the bottom of the modal. This way, if the customers select to delete 1000 clusters, they can simply click the Delete button to confirm, without having to scroll down the list of 1000 clusters to find the delete button.

I also think that a scrollable list is much better than pagination, from a user's perspective

[richard-cox]

General comment. I've seen a modal where they handle this by asking the user to enter <resouce name> and <x> more

[richard-cox]

~Linking this issue to another regarding the generic delete modal - https://github.com/rancher/dashboard/issues/8138~ Misread, that issue bypasses the modal

[richard-cox]

This would be a really nice one to tackle still. I've removed it from 2.7 milestone to get it re-assessed. It also requires UX

[richard-cox]

Should be tackled with https://github.com/rancher/dashboard/issues/9708

[valaparthvi]

General comment. I've seen a modal where they handle this by asking the user to enter <resouce name> and <x> more

I believe I have seen this while deleting multiple GKE clusters in the Google Cloud console, and this is one of the solutions I was thinking of when I opened #9708.