Stop immediately if the target enters the range during ApproachTarget

[TaranDahl]

Stop immediately if the target enters the range during ApproachTarget

• In vanilla, the ApproachTarget will simply exit and do nothing if the target is in range. This will cause your units to approach the target unnecessarily.
• Now you can change this behavior by the following flag.

In rulesmd.ini:

[General]
ApproachTarget.StopWhenInRange=false  ; boolean

[github-actions]

Nightly build for this pull request:

• compiled-dll-f61cffd5a3642266a66f51b82a21196d8c33d527.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

[TaranDahl]

The AttackMove.StopWhenTargetAcquired has been deprecated because it was implemented in an incorrect way. It should be ApproachTarget instead of AttackMove that needs to be modified. It has now been replaced by ApproachTarget.StopWhenInRange. The prerequisite for it to take full effect is #2084.

The AttackMove.PursuitTarget has been deprecated because it was implemented in an incorrect way. It should be InAttackMoveKeepRange (implemented by #2081) and ApproachTarget (implemented by #1998) that need to be modified.

[Coronia]

given there were quite a lot of controversial for our previous tag renaming (such as new Trajectory and the recent major renaming), I think we should still stick to the principal of no tag name change unless necessary. For this PR I think we don't have to depreciate those AttackMove tag, could just redirect their implementaion to the new one.

[TaranDahl]

deprecated because it was implemented in an incorrect way

I don't think we should keep something that is incorrect. This is not a simple tag renaming. They are removed because the function itself is incorrect.