- The projectId only comes back on the annotation in downstream clusters whereas it comes back as both a label
and annotation in the local cluster. This now retrieves the id from the appropriate location and formats it to be
consistent with the existing usage.
- I also noticed that in the local cluster we werent filtering namesapces that are generated by the backend when creating new clusters and projects in downstream clusters. These were prefixed with 'c-' and 'p-' so we filter them as long as they're a system namespace
https://github.com/rancher/dashboard/issues/2500#issuecomment-848267026
- when deleting multiple resources, and confirm enabled, prompt for a random resource name for confirmation
- random resource name will always be visible, for the case where there are more than 5 to delete
- Improved process to declare which resource requires confirmation
- i10n'd some text