Strict major minor version checking on v0 and v1 apis

[ZenGround0]

Related to #7012 #7020 I've been thinking that a step in the right direction is to enforce that new nodes are talking to the same API version both v0 and v1. This won't help the problem of needing to support backwards compatibility for the v0 api for older coder versions but it will prevent nodes from this point onwards from getting too far and erroring in confusing ways when attempting to work against different api versions.

I put this up (1) to see if it breaks CI in interesting ways (2) to get the opinion of @filecoin-project/lotus-maintainers @whyrusleeping and @raulk.

[Stebalien]

Hm. I think strict version checking makes sense for v1, but not v0. v1 is "unstable", so every version can be breaking. v0 is stable, so new versions should be backwards compatible.

[Stebalien]

(well, approved once tests pass)

And we can even use even/odd versioning here as well. I.e., when we're ready to "stabilize" v1, we can cut a v2 that's stable and a v3 that's unstable. That should make it easier to track where we need strict version checks and where we don't.

[magik6k]

Looks like there is some weirdness with Version on lotus-gateway

[ZenGround0]

Yeah the test kit cli testing tool doesn't set the api.RunningNodeType global. Should be fixed now.