Fix 5419: iATM ranges incorrect

[Sleet01]

Initial issue was that iATM weapon bays did not accurately reflect their selected ammo.
In the process of investigating this I discovered a number of issues:

1. iATMs are not covered by most code that handles ATMs
2. iATMs are not considered Streak weapons for Princess planning purposes
3. iATM ammo types are not considered by Princess when guessing at expected damage from prospective attacks
4. ATM and iATM weapon ranges are retrieved, re-calculated, overwritten, and recreated from magic numbers multiple times every turn for each launcher due to redundant code throughout WeaponType, WeaponFireInfo, WeaponAttackAction, and the WeaponPanel GUI elements.
5. The merge of PR Mounted rework #5406 reverted at least some of the Princess ammo selection code; any other code merged after 02/08/2024 is also suspect.

This PR fixes 1-4 and part of 5.

Testing:

• Re-ran all projects' unit tests (note: MHQ unit tests were already failing for other reasons)
• Tested extensively with player-controlled and bot-controlled Aerospace units mounting iATMs
• Built custom Dropships to confirm iATM bays functioning as expected.

Note: appears to be blocked by #5423

Close #5419

[SJuliez]

@Sleet01 Not sure from your inital comment: Is this safer to merge?

[Sleet01]

@Sleet01 Not sure from your inital comment: Is this safer to merge?

Yes.
This will fix the reported issue and restore Princess ammo selection in the current .20 dev branch.
It should also be fine to re-apply if we do end up pulling out the last week of merges and re-building everything.
Also, it appears that a fix for #5423 has already been merged so this should no longer be blocked.