State-machine implementation of umc_mapcycle.txt

[Steell]

This will allow for multiple settings in the UMC-Mapcycle. The file will be read sequentially, when a new setting is found react appropriately.

Ex:

"default_*" -- update the current default setting, affecting all following map definitions

"command" -- Add another command to a list of commands to be executed

etc.

---

Problems with doing this:
Right now, modules know their own settings, and core has no idea of what these are. For this to work, each module would have to sequentially parse the KV each time it is queried for weighting/exclusion. This is quite inefficient.