Investigate the new resource filters

[xing-yang]

Describe the bug

In Velero 1.11, new resource filters for cluster scoped and namespace scope resources are added. There is a plan to deprecate the old resource filters in 1.13 or later. On Supervisor cluster, we currently rely on the old resource filter to exclude CRDs. We need to investigate how this new resource filter affects us.

https://github.com/vmware-tanzu/velero/blob/main/design/Implemented/cluster-scope-resource-filter.md

To Reproduce

[Steps to reproduce the behavior]

Expected behavior

[A clear and concise description of what you expected to happen]

Troubleshooting Information

[Please refer to the Troubleshooting page and collect the required information]

Screenshots

[If applicable, add screenshots to help explain your problem.]

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue]

[xing-yang]

/assign @lipingxue

[xing-yang]

The new filters are: https://velero.io/docs/v1.11/resource-filtering/#--include-cluster-scoped-resources https://velero.io/docs/v1.11/resource-filtering/#--include-namespace-scoped-resources https://velero.io/docs/v1.11/resource-filtering/#--exclude-cluster-scoped-resources https://velero.io/docs/v1.11/resource-filtering/#--exclude-namespace-scoped-resources

Legacy filters and flags: https://velero.io/docs/v1.11/resource-filtering/#--include-resources https://velero.io/docs/v1.11/resource-filtering/#--include-cluster-resources https://velero.io/docs/v1.11/resource-filtering/#--exclude-resources