Factions/ friendly vs unfriendly units

[jomibauer]

The game is about two armies clashing, so the goal here is to have a player controlled army and an army that is not player controlled and hostile. This needs to accomodate more than two armies, though. Once we have AI scripts, there will also be need of a third army that isnt player controlled but is friendly.

• [x] Lists on the Unit Controller to keep track of the enemy, player and other army units
• [x] a new property on the Unit class - allegiance. four string values - "player", "enemy", "friendly_other", "unfriendly_other"
• Player and enemy are obvious. friendly_other are essentially green units -- player can't control them, but they have the same enemy as us. Unfriendly_other is a new faction that could be interesting -- they are AI controlled and hostile to both us and the enemy.
• [x] add a new RangeCheck state
• [x] During the move target state, add a new check for a unit's allegiance when we press "confirm". When their allegiance is to the player, we enter the PathFinding state, but if not, we enter the RangeCheck state.
• [x] Change SkirmishPlayView to be drawn dynamically according to the unit factions involved in the skirmish.
• [x] When we enter the moveTarget state, we need to add a new check of the unitController that looks at the List of player controlled units. When all units are inactive, switch to EnemyTurn state, then Unfriendly_other, then Friendly_other
• [x] Make tiles with enemy units in them be uncrossable by friendly and player units. make unfriendly and enemy units unable to cross any tiles with other-faction units in them.

[jomibauer]

One way to improve on the way the rangeCheck works is to consider not making it a state, but rather storing a list of units to draw ranges for in the moveTarget state. Then I could toggle units range off while still controlling my unit, rather than having to check the range, then turn it off and try to remember where they could move when moving my own unit.