Kurtis Rader a285ef54b4 Validate generated code is up to date ... While working on a change to augment `make lint` to be more comprehensive I noticed that `go generate ./...` produced unexpected errors on my system (see below). This augments the CI environment checks to verify that the generated code is up to date. This also augments the pre-push script to perform the checks by the tools/check-content script run by the CI environment. FWIW: The errors shown below were because my version of the `stringer` tool was out of date (fixed by running `go install golang.org/x/tools/stringer@latest`) Regardless, the point of this change is that the pre-push script and the CI environment should verify that the generated code is up to date. This change adds those checks. > go generate ./... stringer: internal error: package "fmt" without types was imported from "src.elv.sh/pkg/getopt" pkg/getopt/getopt.go:11: running "stringer": exit status 1 stringer: internal error: package "fmt" without types was imported from "src.elv.sh/pkg/md" pkg/md/md.go:163: running "stringer": exit status 1 stringer: internal error: package "fmt" without types was imported from "src.elv.sh/pkg/parse" pkg/parse/parse.go:11: running "stringer": exit status 1 Exception: go exited with 1 [tty 102], line 1: go generate ./...		2022-12-28 13:13:46 +00:00
..
workflows	Validate generated code is up to date	2022-12-28 13:13:46 +00:00