Ensure lists update when switching between workspaces with the same number of rows

[richard-cox]

Summary

Fixes #12437

Occurred changes and/or fixed issues

• Switching between fleet workspaces which contain the same number of resources will fail to update the rows
  • sometimes this would happen anyway, for instance the generation of the resource was updated
• Caused by change in reactivity with base fn in sortable table pagination pipeline
  • this was fired with stale rows (rows from old workspace) BUT would be cached against the new state (new workspace)
  • whenever the pipeline was triggered again (sans other changes) it would then return the cached stale rows
• fixed by providing a specific hash to use instead of one generated on demand (which fetched new state)
  • i've limited this to the workspace world to reduce impact / bugs

Technical notes summary

• this is a quicker fix than re-rewriting the whole thing... or finding out why vue changed behaviour

Areas or cases that should be tested

• Everything list based

Areas which could experience regressions

• Everything list based

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[eva-vashkevich]

Do we need to have a follow up issue to investigate the non-workspace case?

[eva-vashkevich]

this should be kebab case

[eva-vashkevich]

I've tested the original scenario as well as played with namespaces in other areas of rancher and it seems to work but would want someone else to review as well. Also, there is a typo that we should probably fix before merging

[mantis-toboggan-md]

Code-wise this looks safe enough and I've tried testing both fleet workspace switching and explorer namespace switching.

This solution seems appropriate given time constraints but I agree with @eva-vashkevich about filing a follow-up issue to re-evaluate. I'm wary of leaving the root cause of this bug undiscovered but agree with the assessment that it'd take substantial time to do.