Validate server version as same-or-newer instead of strictly equal

[Krinkle]

Allow the version to be semver-major compatible with a newer minor
version. This makes it more obvious in which order changes should
be deployed. I.e. first deploy the WordPress plugin update, and then
(optionally, gradually) update package.json in content repos.

This is partially blocking the ability to enforce use of
package-lock.json, because up until now, jQuery Infra ran npm update
as part of builder's webhook handlers, thus bypassing the lock file.

Once that step is removed, the true version is exposed, and thus
content changes would no longer auto-update. We could mandate that
all content repos (and their older version branches) are always using
the latest version, but I'd rather build a bit more tolerance in the
stack.

Ref jquery/infrastructure-puppet#39.
Ref jquery/infrastructure-puppet#38.

[scottgonzalez]

Ugh, did you update this right away? It's so annoying that there's no notification for force pushes.

[Krinkle]

@scottgonzalez It was 2-3 weeks after my comment, 17 Dec. But yeah, it didn't reset the review state even after "resolving" your comment, and pushing a new commit. 🤷

[scottgonzalez]

Well it's merged and deployed in v1.0.8 now. Thanks.