Fix scaling logic in reconcileNewMachineSetInPlace

[acumino]

What this PR does / why we need it:
Adds a check to ensure the new machine set is scaled up when the combined replicas of old and new machine sets are less than the desired deployment replicas. This basically ensures that if a machine is deleted manually from the old machine sets, a new machine should be created in the new machine set with the updated configuration.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

Fixed an issue where deleting a machine from an old MachineSet could prevent proper scaling. The new MachineSet now scales up when total replicas (old + new) drop below the desired count, ensuring replacements are created with the updated configuration.

[elankath]

thanks for the fix.

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Mark this PR as rotten with /lifecycle rotten
• Close this PR with /close

/lifecycle stale

[aaronfern]

/remove-lifecycle stale

[gardener-robot]

@aaronfern Command /remove-lifecycle is not known.

[aaronfern]

Thanks for the PR!
/lgtm

[takoverflow]

Thanks for the fix! LGTM

Already addressed review comments