Minimal update - Githubissues

Sorry the PR was made in such a rush. Belatedly, here's a run-down of changes for posterity:

patched com_google_protobuf to use zlib-1.2.13. I haven't checked if it was possible to just fast-forward to a usable version, mostly because doing so likely implied other changes. I did follow them a bit, but got to a point where the entire app was updated, but didn't work. So I abandoned that approach for the time being. I still have a branch with that code and may give it another go. The most important update there would be updating to v9 of the go-app framework.
Fixed a small typo protoc -> proto, which introduced a harmless but unnecessary inconsistency between the project name on Github and the go package in use.
Pinned bazel version to 6.3.0 to improve reproducibility. It's annoying to have a dependency on the build system exact version, but the alternative of not knowing which bazel is compatible with the repo is even worse, so this would be an acceptable (to me) way to pin as much of the versioning as possible.
Added runtime flags to ensure that if internal placement of build artifacts changes in bazel (as it does from time to time) that does not break the server side. The location of app.wasm and bootstrap.css is now computed by bazel and passed on to the server. Flags were the most expedient way to achieve that.
Moved the protobuf source from //protos to //protos/api. This makes the package not confuse go mod tidy, so one can use regular go tools to update dependencies (and from there use gazelle to keep things up to date).
Added symlinks into bazel-bin for the generated protos. This makes the bazel setup transparent to go IDE tooling. These are arch specific unfortunately, so you may see things break once in a while. If they do, update the links.
Some accidental reformatting of the source courtesy of my editor running gofmt on save.

grahamjenson / bazel-golang-wasm-proto

Minimal update #3