Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix: fold the expected pod count into addDaemonRequests

addDaemonRequests and expectedPodCount walked the same daemon overhead
groups behind the same "is any instance type still viable" filter, one to
min-fold the overhead and one to max-fold the pod count. Collapse them
into a single traversal. addDaemonRequests now returns the largest daemon
pod count over the groups it considered, and FinalizeScheduling writes the
annotation from that return value.

The annotation write therefore moves after the addDaemonRequests call.
Nothing between the old and new position touches n.Pods or
n.InstanceTypeOptions, so the annotation value is unchanged for every
input.

Also marks the annotation InternalOnly, matching the other annotations
Karpenter writes and users must never set.