Increase NodePool requirements maxItems

[NetanelK]

Description

What problem are you trying to solve?
While working on aws/karpenter-provider-aws#5779 I've reached the maximum limit of 30 requirements per node pool, to support more requirements from providers, the maxItems limit needs to be increased.

karpenter-provider-aws tests should support combined instance type labels.

How important is this feature to you?
This feature is needed to expand karpenter abilities to select instances more granularly.

I'd be happy to contribute this small adjustment if approved.

• 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[NetanelK]

cc @jonathan-innis

[jmdeal]

I believe this limit had to do with CEL limitations around cost estimation. @engedaam do you remember if this was the original reason?