[backport v2.8.next1] Steve socket is spammed on fresh visit to node detail page

[github-actions]

This is a backport issue for #10668, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

Setup

• Rancher version: v2.9-head

Describe the bug

• Rancher now returns a resource.error message when watching an individual resource over websocket
  • See [SURE-7122] Excessive WebSocket activity when watching resources with permission by name rancher#41809
  • Previously it failed to return an resource.error of too old which would result in socket spam
• That revealed a scenario where the ui itself caused the spamming
  • See Steve socket is spammed on fresh visit to a resource detail page #10540
  • Handle the way we get revisions when watching
• That also revealed another bug, which this issue is about
  • The resource.error message is now returned when we try to watch a resource we should not
    • For instance the metrics.k8s.io.nodemetrics resource used in the node detail page
    • The resource.error though isn't one we let stick, so we just try to resource.start / watch again... which results in the same resource.error, repeat ad nauseam
  • Impact
    • This happens on navigate to the node detail page, as opposed to only when refreshing on the detail page
    • The spam does not stop by going from the detail page to the list page. Going from the node detail page where we watch an individual node metric to the node list where we watch all node metrics should behave the same as things like pod ... but it doesn't. Pods will stop the individual watch and start a watch for all.
    • This applies to all resources that we can't watch (no schema watch verb, about 8 out of 182 in a DS rke2 cluster)

To Reproduce

• Bring up a rancher instance at or newer than 793118 (7th March)
• Navigate to the node list
• Bring up dev tools
• Navigate to a node's detail page

Result

• View the messages sent over the cluster socket repeat the resource.start, resource.stop / resource.error, resource.start cycle

Expected Result

• We should not attempt to watch resources the user cannot watch

Screenshots

[IsaSih]

Tested version v2.8-1a77fcd152f1a7bad3ae8e98bb96d96259f41510-head in a k3s single-node cluster on localhost. The resource.error described in the screenshot are no longer displayed. Just wanted to confirm that I can close the issue, but I still see the following resource.errors in the node details page:

Also, the following resource.errors in the node lists:

@richard-cox

[richard-cox]

The Resource error warnings in the console can be ignored, they at some point should not be sent to the UI (see rancher/rancher#40627).

The resource.error messages are sent over web socket, so will appear in dev tools --> Network tab --> WS tab --> /k8s/clusters/<cluster id>/v1/subscribe row's Messages tab

The issue should be resolved if there are no resource.error messages there

[IsaSih]

Tests pass on v2.8-94108186cf35028bb5f7db2c34c5ae99450dad9b-head