Review usages of growl component and update

[richard-cox]

• The growl component flashes up a notification top right. Sometimes this is shown until the user dismisses or is automatically removed
  • Usages: https://github.com/search?q=repo%3Arancher%2Fdashboard%20%22growl%2F%22&type=code
• There's work started to create a new notification process
• We need to confirm usages of growls and if application create issues to remove or port
  • Remove - response should be inline on page close to context instead of in a global notification
  • Port - Should be part of the new notification process

Some examples of usages

• navigation failures (user tries to go to a downstream harvester cluster but there's an error preventing them reaching it, stops a silent failure)
• success after restoring the state of a RKE2 cluster (this is already in a modal, probably needs dropping)
• failure to create an RKE2 snapshot
• form control - unable to open a file after selecting it (possible just needs input based error)
• failure to scale up a workload (given input is a small button in a drop down on a table row)
• result of updating the endpoint of the Azure Auth Provider (??)
• result of rancher upgrade (app-extend.js, would love to know if this still works)
• failure to update groups or members (kicked off by a button above a list)
• errors when installing extensions
• result of installing/deleting extension catalogs
• failure to refresh k8s driver metadata (kicked off by button above a list)
• saving user retention data (should be inline info)
• failure to refresh chart repos (kicked off by button above a list)
• ...about 10 more