...mainly due to arbitrarily failing ci builds, as this doesn't appear
to affect local builds/nix builds on remote builders, just fresh builds
in the ci.
the explanation for why this is happening might be that certain package
VCS's don't allow many/frequent connections from IP ranges other than
GOPROXY's (Google's).
that is sheer speculation, though.
however, it is still true that there are "no" failed ci builds with
GOPROXY env var set to its default value (left untouched), which does
indeed indicate that the above mentioned might be the root cause of the
issue after all.
this commit reverts:
* f3e481395e
and partially reverts:
* 14ba7b18bf
GOPROXY=direct has been kept for `nix-shell`/`nix develop` environments
as that is not where it poses an issue.
also add build status badge to README.md (very important)
---
Squashed commit of the following:
commit 226f181e6dded95357cf3e31c918e811bc6b9bae
Author: surtur <a_mirre@utb.cz>
Date: Wed May 4 16:37:08 2022 +0200
ci: add .drone.starlark
also add build status badge to README.md
