[SPARK-2912] [Spark QA] [WIP] Include commit hash in Spark QA messages

You can find the [discussion that motivated this PR here](http://mail-archives.apache.org/mod_mbox/spark-dev/201408.mbox/%3CCABPQxssy0ri2QAz=cc9Tx+EXYWARm7pNcVm8apqCwc-esLbO4Q@mail.gmail.com%3E). Note that this is a work in progress and will be replaced by a cleaner PR.

As described in [SPARK-2912](https://issues.apache.org/jira/browse/SPARK-2912), the goal of this PR (and related ones to come) is to include useful detail in Spark QA's messages that are intended to make a committer's job easier to do.

Since this work depends on Jenkins, I cannot test this locally. Hence, I will be iterating via this PR.

[Note: This is a duplicate of a [previous PR](https://github.com/apache/spark/pull/1811), without the extraneous commits.]
> sometimes people don't realize their patch wasn't mergeable, it goes through all the tests, and then they have to up-merge it and re-run the tests.

I see. Do you think the built-in GitHub banner is not enough to make this clear? I think adding in little things that save contributors' time as you describe is a good thing, so I'll add it back in if you think it will make a difference.