* Initial support of Germany Cold War terrain
* Updated with latest beacon import
* Updated changelog and ran black
* Fixed the GermanyCW landmap and naming scheme
* Temporarily changed the requirements for pydcs to my branch (will switch back when merged)
* Updated landmap for germanycw with even fewer exclusions
* Removed unnecessary changes
* Updated requirements to lastest pydcs
* Fixed naming issues for Germany
* Update pydcs to latest commit for GCW support
* Add landmap to game.theater.__init__
* Update requirements.txt
* Resolve PyCharm type-waring
* Updated pydcs and exclusion of germany
* Updated land and sea shapefiles for Germany Cold War with new map limits
---------
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
operation_ids give us better function names when generating the
typescript API from the openapi.json. BaseModel.Config.title does the
same for type names. Response models (or 204 status codes) need to be
explicit or the API will be declared as returning any.
We can't directly use frozen dataclasses from pydcs in our interface
because pydantic can't process them. Pydantic is able to automatically
convert to our modelview type from the pydcs type though.
This is briefly moving us over to my fork of pydcs while we wait for
https://github.com/pydcs/dcs/pull/206 to be merged. The adaptation is
invasive enough that I don't want it lingering for long.
A possible explanation for the infrequent CTDs we've been seeing since
adding fast forward is that QWebChannel doesn't keep a reference to the
python objects that it passes to js, so if the object is GC'd before the
front end is done with it, it crashes.
We don't really like QWebChannel anyway, so this begins replacing that
with FastAPI.
