feat(common): add git hash in HealthCheckResponse

[joremysh]

Because

• it helps in debugging with the current running version

This commit

• add git hash in HealthCheckResponse

[linear]

INS-6693 unit tests for pipeline backend

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Nov 8, 2024, 1:30 AM

[jvallesm]

As documented in e.g. vdp, this is a fixed response that I don't think we should customise. I don't think adding this will break anything but I'm hesitant if exposing this in the public API (this endpoint doesn't require authentication) is a good idea.

I think the best approach here is including the revision in the pod definition, then accessing it through kubectl or other tools while debugging.

cc @donch1989 perhaps has an opinion here