Move to natural pom versions

[codefromthecrypt]

Currently, <version>${revision}${sha1}</version> is coded into maven pom files, rendering tools such as jitpack helpless. It would be nice to have normal versions in these files so we have the same chances to use pinot as other java projects. This is particularly important as SNAPSHOT versions are not deployed and docker tags are ad-hoc.

[kishoreg]

+100 for this. @jackjlli can you please explain why this sha was added?

[jackjlli]

The purpose of having revision and sha1 is to have the ability to specify the internal published version of Pinot. By default the revision value is the next release version (like 0.5.0) and the sha1 value is -SNAPSHOT. In LinkedIn, we leverage this to change the version to an internal release (like 0.5.0-dev-12345) and then publish the release to internal artifactory.
I actually have a PR which moves to natural pom versions: #5840 but the logic is mixed with migrating the publication. I can split that out to a separate PR.

[jackjlli]

Just split that logic out of the previous PR:
#5945
Could @kishoreg @adriancole take a look? Thanks!