R2: Refit Refit

[WeaverThree]

Rebuild the entire refit system from the ground up to use a list of RefitStep objects that represent the, well, steps that you have to go through to make the refit happen. This makes it (i think) easier to analyze the units involved in the refit and then carry out the refit when the time comes.

Work completed so far includes:

• A couple of large enums to represent refit classes and refit step types, that encapsulate as many lookup-table type features as possible.
• Analysis of differences between starting and target units for refits. (The hardest part)
  • Including dealing with things like CASE that aren't represented well.
  • Ammobins and Armor are a special pain too
  • Dealing with damaged locations not accepting new parts unless they're being replaced. So you can replace damaged endo steel without replacing it, but not weasel around repairing your broken shoulders in other cases.
  • Should cover all your part needs from warships to LAMs, but I'm not sure every single thing is accounted for properly yet.
  • Omni refit analysis, finding which refits are able to be omni repods and which need to be factory level recustomizations.
  • Omni refits ignore armor damage when applicable. (On a normal refit, armor gets refreshed as a bonus, since we might have been changing it anyway).
• Optimization of parts needed and parts taken off of the unit.
• A whole new window to manage refits in. It's full of slide views! More stuff than can even fit in view at once too, so we have tabs. A lot of work on making the display as good as possible.

Things left to do:

• Double check omni-pod handling on non-omni refits.
• A class to represent a refit kit, that can contain the items/value required for a kit refit. Not going to be using the Refit class itself because that seems to be an easy way to cause problems.
• Actually ordering goods to initiate the refit
• Saving/loading refit status and the steps list
• Dealing with loading older save data and converting old refits in progress
• Actually carrying out the change in units when the refit completes
• Refurbishment, which should be an alternate code path that is easier
• Canceling refits
• Saving customization files, which may get punted over to MekLab
• MekLab integration. (Adding a tab to it with all this info, hopefully)
• Rewrite all the refit tests?

At this stage it should be possible to examine any possible refit and see if the steps are what they should be, but actually attempting to carry out a refit will probably set something on fire.

Here are some screenshots that show how it works, to some degree.