Make the go version check better support multi-version go installs

[ValarDragon]

Cref: #3634

This PR breaks all users who have an up-to-date version of go on their build hosts. One can fetch older Go versions and call them as e.g. go1.18 build ..., which would in theory solve the problem here, but it doesn't work because the Makefile doesn't parameterize calls to the go tool.

Quick fix would be

GO ?= go

GO_MAJOR_VERSION = $(shell ${GO} version | cut -c 14- | cut -d' ' -f1 | cut -d'.' -f1)
GO_MINOR_VERSION = $(shell ${GO} version | cut -c 14- | cut -d' ' -f1 | cut -d'.' -f2)

$(BUILD_TARGETS): check_version go.sum $(BUILDDIR)/
	${GO} $@ -mod=readonly $(BUILD_FLAGS) $(BUILD_ARGS) ./...

with equivalent changes (go → ${GO}) throughout the file.

Originally posted by @08d2 in #3634 (comment)

[ValarDragon]

An alternative is in the build check, to try go1.18 in the install when go is the wrong major version (and otherwise report an error, and tell the user to run go1.18

[08d2]

To be clear, these are temporary hacks, and cannot be relied upon. Osmosis must build and run successfully with the latest major version of Go. Whatever prevents that is a bug that must be fixed.

[ValarDragon]

I agree for the sort & compression issues. (The sort should tbh be pretty basic to fix)

If theres FFI issues similar to whats changed in the past, that may genuinely be unavoidable.