Support for Git commit hashes when building BlazeVersionData

[odisseus]

Checklist

• I have filed an issue about this change and discussed potential changes with the maintainers.
• I have received the approval from the maintainers to make this change.
• This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.

Discussion thread for this change

Issue number: #7133

Description of this change

[tpasternak]

Well, it's a blaze client version, I would prefer to keep it null.

[tpasternak]

This way is just putting sort-of-a-random-number there which can backlash in future. Particularly because the order seems to matter (there is a method blazeClientIsAtLeastCl)

[odisseus]

You are right, the commit prefixes have no particular order, so my code violates that expectation. We could try to find the latest tag, or the commit date, but there is no guarantee that they will be ordered either.