Add commit hash to debug version string

[RichardAH]

High Level Overview of Change

With so many people experimenting with different builds, it can be hard to track which build corresponds to which specific code change. To this end adding the commit hash to the version string when building using -DCMAKE_BUILD_TYPE=Debug will help reduce confusion and human error.

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

[RichardAH]

We might consider actually adding the git commit hash to the release version string as well, it will assist in debugging the live network

[nbougalis]

I'm fine with this as is (upto my comment) but it might also be interesting to:

a) look at reworking the 64-bit encoded version, so that it can include the commit ID; and
b) decide whether the commit ID should be included in getVersionString or only in getFullVersionString.

[nbougalis]

Is it really your intention to have this block only added when compiling builds with DEBUG or SANITIZER support? If not, you should probably move this block up to line 38.