koord-yarn-operator: add cache filter in Manager to reduce memory occupied by the koord-yarn-operator.

[tan90github]

Ⅰ. Describe what this PR does

When we used yarn-operator internally for yarn mixing, we found that the yarn-operator component took up a lot of memory. Through pprof inspection, we found that ListAndWatch took up a lot of memory. Finally, we found that the reason was the field index. Therefore, we modified the default Cache so that the field index only focuses on the NMpod of interest.

before:

after:

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it

Ⅳ. Special notes for reviews

V. Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests
• All checks passed in make test

[tan90github]

PTAL @zwzhang0107

[tan90github]

cc @j4ckstraw @yangfeiyu20102011

[stale]

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close
  Thank you for your contributions.