feat: add evictAfterOOMThreshold per vpa

[omerap12]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

evictAfterOOMThreshold is now per vpa 

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[AEP]: https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/enhancements/8026-per-vpa-component-configuration

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: omerap12

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• vertical-pod-autoscaler/OWNERS [omerap12]
• vertical-pod-autoscaler/pkg/apis/OWNERS [omerap12]

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

[omerap12]

/hold
/kind api-change
/label api-review

[soltysh]

Initial comments from API shadow

[soltysh]

I don't think we have any metav1.Duration in the k/k APIs, and from a quick grep it seems we don't have them in this repo. So I'd suggest to stick with the usual units as described here https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#units. Example EvictAfterOOMSeconds or something like that.

[adrianmoisey]

I've added noduration to kube-api-linter: #9147

[adrianmoisey]

I don't know if this matters, but, this field is an override to the --evict-after-oom-threshold flag, which is currently a duration:

autoscaler/vertical-pod-autoscaler/pkg/updater/priority/update_priority_calculator.go

Lines 41 to 43 in e8fe343

	evictAfterOOMThreshold = flag.Duration("evict-after-oom-threshold", 10*time.Minute,
	`Evict pod that has OOMed in less than evict-after-oom-threshold since start.`)
	)

Keeping the flag and API constant feels like a nice thing to do, but I'm assuming the reason listed in the api-conventions doc is higher priority:

We don't use Duration in the API since that would require clients to implement go-compatible parsing.

[omerap12]

Thanks Maciej (again) :)
@adrianmoisey , so let's go with EvictAfterOOMSeconds? I will update the AEP and this PR if that's ok with you.