Quick fixes for degenerate behaviour in rebelAttack

[jaj22]

What type of PR is this.

1. Bug
2. Change
3. Enhancement

What have you changed and why?

The four small attacks against easy targets option and wave count calculation were not working as intended. I've removed the former and simplified the latter to temporarily fix the behaviour. Example cases that now work reasonably:

• Small attacks not spawning due to HC maxUnits limits so the attack does nothing.
• Only one small attack spawning and being less effective than a wavedCA for a higher timer cost.
• Depending on the size and grouping of the singleAttack, captured target will often have a very small garrison afterwards and so be very easy to recapture.
• With 1-3 easy targets, the code would always prefer a non-easy target, often leading to useless attacks on cities.
• Long distance targets having very large wave counts, even if very early game.
• Short distance targets having minimal wave counts, even if heavily defended.

It's not ideal, but I don't think there's any practical downside.

Please specify which Issue this PR Resolves.

closes #2142

Please verify the following and ensure all checks are completed.

1. Have you loaded the mission in LAN host?
2. Have you loaded the mission on a dedicated server?

Is further testing or are further changes required?

1. No
2. Yes (Please provide further detail below.)

How can the changes be tested?

Difficult because attacks targets are deterministic but target side is random, and there's no function separation. In general, set up various situations with markerChange and garrison functions and then run [attackerSide] spawn A3A_fnc_rebelAttack. Using reb vs gov to constrain the target side may be useful.

Not really any new code here though, just removal of paths.

[HakonRydland]

looks resonable