Ensure extensions can easily make use of server-side pagination and vai-based api features

[richard-cox]

• Documentation covered in other issues (replacement of findAll, use of common components like list and labelSelector filters that make use of ssp, etc)
• ATM pagination is restricted to certain types / situations
• This ensures that we can port of required functionality (like table headers) before enabling
  • See shell/utils/pagination-utils.ts isEnabled
• For CRDs that don't have their own list component (and possibly broken headers) SSP will be on
  • There's no difference between those types and the ones we show in More Resources
• For CRDs that have custom lists though they would need to update a setting to enable the whole store (not possible for cluster, but if they had a custom one like harvester) OR specific types by updating a performance setting
  • This has to be improved / extensible