Use quantity library and optional types once 1.28 reaches EoL

[IrvingMg]

What would you like to be cleaned:

1. We can remove the validation functions implemented for ClusterQueue in fields with resource.Quantity type.
2. Additionally, we can shorten some rules that use the macro has() to check an optional field exists.

Why is this needed:

1. Since Kubernetes 1.29, we can use Kubernetes quantity library to validate fields of resource.Quantity type.
2. Likewise, we can rewrite some rules to make them more concise using CEL optional types.

Discussion:

• Add CEL rules to ClusterQueue #1972 (comment)
• Add CEL rules to Workload #2008 (comment)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tenzen-y]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tenzen-y]

/remove-lifecycle stale