Project Scoped Secrets not applying filter selection

[IsaSih]

Setup

• Rancher version:
  Rancher v2.12.0-alpha21
  Dashboard v2.12.0-alpha15
  Rancher CLI v2.12.0-rc.1

Describe the bug
The project secrets table displays secrets that do not respect the namespace filter selection. This happens in both the local and downstream clusters. The filtering works as expected for the Secrets table, not for the Project Secrets table

To Reproduce
Create Project Scoped secrets (both in local and downstream clusters) in different Projects and namespaces.
Try to filter the Project Scoped Secrets by a project or a namespace and compare it with the Secrets list.

Result

https://github.com/user-attachments/assets/3e210092-8e80-4052-b3dd-1feb8cb214c8
https://github.com/user-attachments/assets/7de50b55-4be7-4748-8731-d8a3b8092f3d

Expected Result
The Project Secrets table should only display secrets that belong to the corresponding filter selection

[richard-cox]

Project scoped secrets aren't namespaced, though are associated with a project.

We would need to do some funky plumbing to get ns change notifications, and to also then apply a different filter (locally and to http requests)