Be good citizens and test Kubo with Go RCs

[Jorropo]

We currently have a policy of never updating to go1.X.0 releases, that means we wait for go1.X.1 or later.
This is due to a few times breaking changes were added to the STD that broke Kubo's behavior, thankfully caught by our extremely extensive test suite.

Instead we should:

• Run RCs of Go but accept merging PRs with theses failings
• Debug new test Failures
• If they are bugs in Kubo that were caught by hardening of Go, fix them.
• If they are bugs or behavior changes in Go or the Std, report them.
  • Sometimes breaking behavior is done on purpose and sometimes for good reasons also, then we should fix it in Kubo.

Hopefully that means theses bugs would be able to be fixed before the first release of Go, things in Go are also more malleable during in the RC phase compared to after a go1.X.0, improving the ecosystem as a whole and not having a situation where we purposely stick with the go1.(N - 1) release due to last minute costy changes that needs to happen. (Kubo v0.22 has been released using go1.19.12 while go1.20.7 was available for a very long while due to a last minute discovery of golang/go#60674, we are now fixing this in #10068)

---

The reason we did not do that in the past is due to quic-go which was forking the crypto std and having manual compatibility using unsafe, this required, this is now fixed for future releases with golang/go#44886.

---

Blockers:

• Support go1.21.0 #10064

[Jorropo]

For now we are blocked on our 1.21.0 support, go is in the merge phase so this is a good timing to bring us back up to the latest release of go so we are ready for the next RC phase.

[marten-seemann]

This is great! Can't wait to see this happen. And super happy that with the switch to crypto/tls, quic-go won't be blocking this any more in the future.