Remove exit after scale-up is performed

[BigDarkClown]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Static Autoscaler has been exiting RunOnce method early in case of scale-up, either successful or unsuccessful. This made scale-down not run in loops were scaling up was attempted.

This can cause issues with persistently failing scale-ups blocking scale-down in the cluster. I don't believe there are any reasons why we would need to keep this early-exit logic.

Special notes for your reviewer:

Please advice if you have any intuition on what could potentially break after this change. I believe the snapshot logic should be able to maintain consistent cluster state after attempting scale-up, so I don't see a reason why scale-down could fail after that.

Does this PR introduce a user-facing change?

Remove early-exit from control loop after scale-up attempt, enabling scale-up and scale-down to be performed in a single loop

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BigDarkClown

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cluster-autoscaler/OWNERS [BigDarkClown]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment