Configurable Karpenter nodepool consolidation policies

[cnmcavoy]

Description

What problem are you trying to solve? Karpenter provides nodepools with a disruption spec to control how a nodepool can be disrupted by Karpenter to satisfy nodes.

As a cluster operator, I want to be able to configure certain nodepools for only single-node consolidation (consolidation for cheaper instance types), and other nodepools for only multi-node consolidation (consolidation for larger instance sizes).

Motivation: We've found that single-node consolidation tends to lead to unnecessary or unproductive churn in large nodepools, but there are certain use-cases it is valuable for. So for most of our Karpenter nodepools, we want to be able to switch off the single-node consolidation, but leave the multi-node and emptiness consolidation in place.

How important is this feature to you?

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[k8s-ci-robot]

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.