Avoid running traffic increase hooks after the last increase step has already been completed (and analyzed)

[pereiratps]

This PR is an improvement on the PR #1470 which was released in version v1.33.0.

The goal is for the traffic increase webhook to only run when the next step is actually a traffic increase.

Without this change, Flagger will still be calling the traffic increase webhook even after the last increase step has already been analyzed, right before the verification promotion webhook.

The code logic can be compared with the promotion webhook call (already on the code):

flagger/pkg/controller/scheduler.go

Lines 591 to 595 in dfc0c96

	if canaryWeight >= maxWeight {
	// check promotion gate
	if promote := c.runConfirmPromotionHooks(canary, canaryController); !promote {
	return
	}