But, as it turns out, the uses of this code and data are very minimal.
No-one's been complaining about things being out of date or not working.
All of these *_map dictionaries are just for mapping parts of module
identifiers to English Text. In the end they only end up in the output of
`EDMC.py -e <file>`, which despite being called "E:D Shipyard plain text
format" isn't actually supported by edsy.org.
A simple HTTP handler has been added that will dump any and all POST
data it gets to EDMC's log.
Additionally, a new command line argument to switch EDMC to using this
as its EDDN target has been added.
They're the same key, and value, as the ES ones. PyCharm highlighted
this, flake8 did not complain. There's a comment as to why they're
commented out, but still present in that form.
The full string for the Flightsuit is 'Traje de vuelo', and we indeed
have 'Traje' as the translation for 'Suit', so the UI comes out as
'Traje: de vuelo' for this.
I've gone with 'None' for when there's no data, rather than {}. That
makes for simpler checks on if there is data (a dict.get('foo') only
checks for that, not the dict structure otherwise).
If no 'suit' in the data we assume no Odyssey, but otherwise plough on
with dict.get() statements as they'll default to None if it's not
present.
*Users* of this monitor.state[] extra data get to choose what to do if
some data is present but not other.
Also refactors data.py to edmc_data.py as I'm having weird issues with
PyCharm debugger not starting, and this seems to be to do with module
name clashes.
