adding hack to add git hashing to report

[jaredeh]

In the Storage WG meeting I made a suggestion for having the benchmark check the code. This is an example of how that could work. It will add a 'git' section to the .json report with a git hash and if relevant a diff showing what has been changed.

[github-actions]

MLCommons CLA bot:
Thank you very much for your submission, we really appreciate it. Before we can accept your contribution, we ask that you sign the MLCommons CLA (Apache 2). Please use this [Google form] (https://forms.gle/Ew1KkBVpyeJDuRw67) to initiate authorization. If you are from an MLCommons member organization, we will request that you be added to the CLA. If you are not from a member organization, we will email you a CLA to sign. For any questions, please contact [email protected].
0 out of 1 committers have signed the MLCommons CLA.
❌ @jaredeh
_{You can retrigger this bot by commenting recheck in this Pull Request}

[jaredeh]

recheck