https://linear.app/sourcegraph/issue/DINF-111/rework-how-we-inject-version-in-our-artifacts

Pros:

• saves having to rebuild bazel query 'kind("go_library", rdeps(//..., //internal/version))' | wc -l == 523 Go packages when stamp variables cause a rebuild
• Cutting out GoLink action time when stamp changes but code is cached

Cons:

• Binaries themselves are no longer stamped, only knowing their version info within the context of the docker image
• A tad extra complexity in internal/version/version.go to handle this new divergence

Before:

$ bazel aquery --output=summary --include_commandline=false --include_artifacts=false --include_aspects=false --stamp 'inputs(".*volatile-status\.txt", //...)'

  Action: 1
  Genrule: 2
  Rustc: 3
  ConvertStatusToJson: 88
  GoLink: 383

After:

$ bazel aquery --output=summary --include_commandline=false --include_artifacts=false --include_aspects=false --stamp 'inputs(".*volatile-status\.txt", //...)'

Mnemonics:
  Genrule: 2
  Action: 3
  Rustc: 3
  ConvertStatusToJson: 86

Test plan

Lots of building & rebuilding with stamp flags, comparing execution logs & times

Changelog