wrapdb server static v1 api mirror and nginx config update

[tp-m]

See #1768 for background.

Content of this MR is basically from https://github.com/tp-m/wrapdb-v1-api-mirror/, seems better to have it right here in the repo next to the nginx config.

Closes #1768

[eli-schwartz]

I'd prefer to avoid having all these files directly checked into git, though. e.g. we use GitHub Releases to store the ZIP files for all current releases because checking them into git tends to be rather suboptimal usage of git's object storage design.

[tp-m]

Understood, but I'm just trying to document what's deployed right now on the server, so that it's easily possible to replicate the setup on a new machine if ever needed.

The size of the .zip files here is 977kB and that will not change going forward, since the v1 archive is frozen now.

If someone wants to make sure that all v1 zips (incl. sqlite) are available on github, so we can add redirects for them a la this be my guest.

In the meantime I'm just documenting what's what, and seeing the fairly small size I don't think it's worth worrying about too much.

[bgilbert]

Since these are derived artifacts of this repo, and not intended to change, it does seem awkward to commit them here as though they're the canonical editable copy. Keeping them in a separate Git repo seems to make sense - maybe we should just add some documentation pointing to https://github.com/tp-m/wrapdb-v1-api-mirror/?

[tp-m]

Since these are derived artifacts of this repo, and not intended to change, it does seem awkward to commit them here as though they're the canonical editable copy. Keeping them in a separate Git repo seems to make sense - maybe we should just add some documentation pointing to https://github.com/tp-m/wrapdb-v1-api-mirror/?

Sure I can do that, just thought we might want to have everything together in one place.