Vaarn SRD URLs

[Gulluth]

I just noticed that the URLs in Vaarn Atlas now land on 404 pages after the SRD was overhauled, and the URLs will need to be updated to the new locations.

[Gulluth]

At first glance this was a simple resource file update. I didn't want to install the full Unity toolchain locally, so I thought it would make sense to build a devcontainer so this could be built locally in Docker, or on github Codespaces.

I've run into a blocking issue with this approach which is the version of Unity to build Vaarn Atlas uses a version of glibc (in the docker container) that is too old to be supported by devcontainers. There is a workaround, but it is quite hacky and involves creating a build root with glibc from a newer version of ubuntu. Instead of taking this hacky approach, it would be better to update the project to Unity LTS 2022.3 which has a build container using a newer version of Ubuntu.

This is a simple Unity project, so updating to a newer version of Unity should not be very problematic, but there are some specific changes the project will need:

• TextMeshPro: In 2022.3 TMP ships as a built-in package rather than a separate install. Existing scenes should import fine but need to verify text renders correctly.
• Post Processing: com.unity.postprocessing 3.x still works in 2022.3 but it's legacy. A fresh project would use the Volume system, but migrating existing scenes is optional.
• SyncVS.SyncSolution(): Deprecated in 2022.3 and would need one line changed to Unity.CodeEditor.CodeEditor.Editor.CurrentCodeEditor.SyncAll() in the devcontainer.
• Package versions: manifest.json package versions would all auto-resolve to newer compatible versions the first time Unity Editor 2022.3 is launched.

[Gulluth]

• Unity bumped to 2022.3 LTS
• devcontainer.json added with instructions for adding unity license
• bugfix: a map generation "out of bounds" crash has been fixed

• bugfix: initial overland render geometry has been fixed.