Units AutoDeploy/DeployBlock on Ammo change

[Fryone]

Requires units to have:
'Ammo' > 0;
'IsSimpleDeployer=yes';
'Convert.Deploy='.

IsSimpleDeployer vehicle auto-deploy / deploy block on ammo change

• Vehicle deployment can now be affected by ammo count.
  • Ammo.AutoDeployMinimumAmount determines the minimal number of ammo at which a vehicle converts/deploys automatically.
  • Ammo.DeployUnlockMinimumAmount determines the minimal number of ammo that unlocks issuing vehicle converting/deploying command.
    • Ammo.AutoDeployMaximumAmount and Ammo.DeployUnlockMaximumAmount behave analogically.
    • Setting a negative number will disable ammo count check.

In rulesmd.ini:

[SOMEVEHICLE]                        ; VehicleType
Ammo.AutoDeployMinimumAmount=-1      ; integer
Ammo.AutoDeployMaximumAmount=-1      ; integer
Ammo.DeployUnlockMinimumAmount=-1    ; integer
Ammo.DeployUnlockMaximumAmount=-1    ; integer

Auto-deploy feature requires `Convert.Deploy` from [Ares’ Type Conversion](https://ares-developers.github.io/Ares-docs/new/typeconversion.html) to change type. Unit without it will constantly use deploy command on self until ammo is changed.

IsSimpleDeployer vehicle ammo change on deploy

• Ammo.AddOnDeploy determines the number of ammo added or substracted on unit deploy.

In rulesmd.ini:

[SOMEVEHICLE]           ; VehicleType
Ammo.AddOnDeploy=0      ; integer

[MortonPL]

Looks good, a few minor style and documentation issues remain.

[Metadorius]

It would also be good to have this feature at both "sides" of the ammo count, as in instead of
specifying the minimal required amount you can also specify the maximum.

[Otamaa]

Seems good to me !