Commit Hash in Docker Image

[stanbrub]

• Added the deephaven-core SHA the build-ci.yml and edge-ci.yml workflows
• Used COMMIT_HASH in server and server-slim contexts and hcls
• Tested Branch CI on my fork. Commit hash appears in manifest:
  • ex docker container inspect ddb093257e90 shows output that contains
  • "org.opencontainers.image.revision": "71646c35b2987e83cf34b53b632498b8aba21332"
• Only server and server-slim were changed. Do we need any more?
• Release CI was not touched (I did come up with a possible way.)
  • ex. curl https://api.github.com/repos/deephaven/deephaven-core/commits/v0.35.0 | grep '"sha":' | head -1 | cut -d'"' -f4

[devinrsmith]

I think to move this label should only apply to edge / branch builds (using the Dockerfile split staging construct mentioned earlier). Also, does everything work if GIT_REVISION is set to an empty string instead of "not-set"?

[devinrsmith]

Also, for the release, we probably technically want to point to the tag revision and not the commit revision, if we were to add the LABEL for the release. I could probably argue we should use the tag name (as opposed to the revision SHA) for the GIT_REVISION for release images, but regardless, we would want to do that separately from this PR.

$ git rev-parse v0.35.0     
33d520aef42bc92d22bd5190511dbc6b67f87043

$ git rev-parse release/v0.35.0
d7a2af575e3dfbbc2c429c546c66e783c93358a5

Note the difference.

[devinrsmith]

LGTM. Please write a merge message describing this a bit more succinctly.