build failed: panic: qtls.ClientHelloInfo doesn't match

[eval-exec]

Describe the bug:

failed to build visor.

Steps to Reproduce:

❯ uname -a
Linux mufasa 5.10.60-1-lts #1 SMP Fri, 20 Aug 2021 21:04:02 +0000 x86_64 GNU/Linux
  ~/github.com/filecoin-project/lily on  #v0.7.7                                                                                                                                                                                                          !1/19 at  10:00:09
❯ go version
go version go1.17 linux/amd64
  ~/github.com/filecoin-project/lily on  #v0.7.7                                                                                                                                                                                                          !1/19 at  09:55:13
❯ git status
HEAD detached at v0.7.7
nothing to commit, working tree clean
  ~/github.com/filecoin-project/lily on  #v0.7.7                                                                                                                                                                                                          !1/19 at  09:56:35
❯ make build
rm -f visor
go build -ldflags="-X=github.com/filecoin-project/sentinel-visor/version.GitVersion=v0.7.7" -o visor -mod=readonly .
  ~/github.com/filecoin-project/lily on  #v0.7.7                                                                                                                                                                                               took  8s  !1/19 at  09:56:48
❯ ./visor -h
panic: qtls.ClientHelloInfo doesn't match

goroutine 1 [running]:
github.com/marten-seemann/qtls-go1-15.init.0()
        /home/vory/go/pkg/mod/github.com/marten-seemann/qtls-go1-15@v0.1.1/unsafe.go:20 +0x132

Visor Version: v0.7.7

[frrist]

$ go version
go version go1.17 linux/amd64

lily currently expects (and builds for) go v1.16

lily/go.mod

Line 3 in 8c740e0

go 1.16

I've filed #680 to track the work to support v1.17, closing as v1.17 isn't supported at this time (and we'll likey need to wait for dependencies of lily to upgrade as well).