[maraino]

This PR updates crypto and migrates to go-jose v4, fixes the regressions the migration introduced, and moves the development tools to go tool.

Note that this branch syncs certificates@master. We will change this to a release tag before releasing the new version.

Breaking changes

go-jose v4 is stricter about oct keys, which affects existing keys:

• HMAC keys: keys must be at least 32 bytes for HS256, 48 for HS384, and 64 for HS512. Shorter keys no longer work with step crypto jwt and step crypto jws sign and verify, and --insecure does not override the minimum in jwk create.
• AES key wrap keys: the key size must match the algorithm exactly, which is 16, 24, or 32 bytes. jwk create enforces this, and jwe decrypt rejects existing keys that do not match. This includes keys that earlier versions created with --alg A128KW, A192KW, A128GCMKW, or A192GCMKW and no --size, which were 32 bytes.

Fixes

• Token inspection: go-jose v4 rejects unlisted algorithms when parsing, so jwt inspect, jws inspect, and jose format could no longer show tokens using none, ES256K, or unknown algorithms. They now use the new internal/joseutil parsers, which only relax the algorithm check. jws verify and jwt verify stay strict, and tests cover this. These helpers could move to crypto later.
• jwk create --size: oct sizes are validated with errors that point at the flag and name the unit. The 16-byte minimum for algorithms with no size of their own, like dir, is restored. The help now says bits for RSA and bytes for oct, and the shared --size flag only describes RSA, as the other commands do not support oct.
• jwe encrypt with oct keys: it always failed with unsupported key type '<nil>', also on master, because JSONWebKey.Public() returns an empty key for symmetric keys.
• jose format: it reordered the protected header when serializing, also on master, which invalidated the signature or authentication tag. It now keeps the original header.
• --size errors: a size of 0 no longer reports "must be greater than or equal to 0" for RSA.

Tools

golangci-lint, goimports, govulncheck, and gotestsum are now defined in go.mod and run with go tool, as in other smallstep repositories. make bootstrap only installs GoReleaser Pro, and CI uses the same golangci-lint version. The modules compiled into step do not change.

A local go.work that uses this module fails with an ambiguous import of cloud.google.com/go/compute/metadata, because golangci-lint brings in an old compute through viper. Builds without a workspace, including CI, are not affected.

Reviewing

The commits are separate to make this easier to review. Format imports using the local prefix only changes import grouping in 85 files, after make fmt started using github.com/smallstep/cli as the local prefix, so it can be skipped.

Related: smallstep/crypto#1157