This is a partial revert of rP22351, which skipped the "MoveToTargetAttackingRange" in APPROACHING. I (incorrectly) assumed that the original order was still perfectly fine, but in fact the attacker's max range may have changed as that depends on the relative elevation between attack and target - and so the original order might never get us in range!
This was introduced right from the start in rP13626 - so I must assume it was intentionally done to fix this very issue.
I have added a comment so that future readers won't do the same mistake.