[feat] Fieldspec filter supports wildcard match

[yuwenma]

more context in #4456

@KnVerey @natasha41575 Let me know how you feel about this approach. If it is okay, I'll add unittest and am happy to extend the wildcard feature to fieldspec based filters (like fieldspec, fsslice, etc) as well

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yuwenma
To complete the pull request process, please assign natasha41575 after the PR has been reviewed.
You can assign the PR to them by writing /assign @natasha41575 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@yuwenma: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
kustomize-presubmit-master	971e558	link	true	/test kustomize-presubmit-master

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[natasha41575]

Thanks! I left a comment on #4456

[yuwenma]

Per offline discussion, kustomize will not support fieldspec-level wildcard match from the perspective of avoiding users to do unstructured editing https://kubectl.docs.kubernetes.io/faq/kustomize/eschewedfeatures/#unstructured-edits

@KnVerey @natasha41575 Correct me if the comment is inaccurate and feel free to add rationales.