Add git commit hash to version output

[rynowak]

Describe the proposal

We should add the git commit hash to the version output of both dapr --version and daprd --version

As an example here's what kubectl does:

➜ kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.1", GitCommit:"c4d752765b3bbac2237bf87cf0b1c2e307844666", GitTreeState:"clean", BuildDate:"2020-12-19T07:38:38Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-16T20:43:08Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}

We don't need to adopt JSON as a format - the takeaway here is that you can verify the supply chain of what you're using exactly. This is important for the team doing verification of a release - you can know what version you have exactly.

Release Note

RELEASE NOTE: ADDED git commit hash of cli and runtime to --version output

[mukundansundar]

@rynowak I agree. This also needs a fix in dapr/dapr repo.

[mukundansundar]

Also consider adding the runtime api version to the output.

[dmitsh]

/assign

[wcs1only]

I think we need to treat this as a breaking change if we were to change the format of the dapr --version output. Users CI/CD pipelines may already be depending on the current output format.

Perhaps if we were to add a --build-info flag that contained this information in a structured and therefore extendable format?

[wcs1only]

Say I were a customer with a CI/CD script like this:

VERSION=$(dapr --version | awk -F ': ' '/Runtime/ {print $2}')
echo $VERSION

We can't have this change be breaking integrations like this, can we?