Add conditional depagination by native api, apply to bindings

[richard-cox]

Summary

Fixes #11024

Occurred changes and/or fixed issues

• Support conditionally de-paginating resource lists
• Apply conditional de-pagination to cluster and project bindings. Counts of either over 5000 will mean NO de-pagination happens
• This will ensure users with an amount of resources that the UI can reasonable fetch and cache... are fetched. For users with too many the current functionality continues (some bindings will be missing)
  • In the next feature release these changes will most probably be reverted and server-side pagination is used instead

Technical notes summary

Main change

• change depaginate type setting from boolean to boolean | function
• depaginate function will conditionally return true
• currently condition only supports a pre-defined count (don't de-paginate if there are too many resources)

In addition / supporting changes

• fix currentProduct(resource) getter lookups for norman cluster and project roles (they returned cluster instead of rancher, affected by case sensitive type name)
• fix for some cases where we were creating or viewing norman resources and trying to call steve only fetchResourceFields

Areas or cases that should be tested

Resource	Count	Expectation
Cluster Bindings	under 1k	Cluster --> Cluster and Project Roles --> Cluster Tab. All results should show (it should be enough just to check the of X Cluster Memberships in pagination control at bottom)
Cluster Bindings	over 1k and under 5k	Cluster --> Cluster and Project Roles --> Cluster Tab. All results should show (it should be enough just to check the of X Cluster Memberships in pagination control at bottom)
Cluster Bindings	over 5k	Cluster --> Cluster and Project Roles --> Cluster Tab. Only 1k results should show (it should be enough just to check the of X Cluster Memberships in pagination control at bottom)
Project Bindings	under 1k	Cluster --> Cluster and Project Roles --> Project Tab. All results should show (it should be enough just to check the of X Project Memberships in pagination control at bottom)
Project Bindings	over 1k and under 5k	Cluster --> Cluster and Project Roles --> Project Tab. All results should show (it should be enough just to check the of X Project Memberships in pagination control at bottom)
Project Bindings	over 5k	Cluster --> Cluster and Project Roles --> Project Tab. Only 1k results should show (it should be enough just to check the of X Project Memberships in pagination control at bottom)

Areas which could experience regressions

• Create and then view any resource type, no errors in console

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

[richard-cox]

remove opt

[nwmac]

LGTM