Binaries built without CGO will not use BoringCrypto as expected

[strideynet]

hack/build-spike.sh:

CGO_ENABLED=0 GOEXPERIMENT=boringcrypto go build -o keeper ./app/keeper/cmd/main.go
CGO_ENABLED=1 GOEXPERIMENT=boringcrypto go build -o nexus ./app/nexus/cmd/main.go
CGO_ENABLED=0 GOEXPERIMENT=boringcrypto go build -o spike ./app/spike/cmd/main.go
CGO_ENABLED=0 GOEXPERIMENT=boringcrypto go build -o demo ./app/demo/cmd/main.go

Here, we specify CGO_ENABLED=0 for the building of most binaries, but, we also specify GOEXPERIMENT=boringcrypto. This combination causes the binary to be silently built without boringcrypto!

We should adjust all binaries to be built using CGO, or, build them without specifying boringcrypto.

I'd suggest that if we're not immediately aiming to be FIPS-compatible, we may want to drop boringcrypto, and wait for golang/go#69536

[v0lkan]

All good suggestions.

We can at least make all of the binaries CGO enabled as a low hanging fruit maybe.