Expose aplication ID in ApplicationStart event, use it in history server.

This change exposes the application ID generated by the Spark Master, Mesos or Yarn
via the SparkListenerApplicationStart event. It then uses that information to expose the
application via its ID in the history server, instead of using the internal directory name
generated by the event logger as an application id. This allows someone who knows
the application ID to easily figure out the URL for the application's entry in the HS, aside
from looking better.

In Yarn mode, this is used to generate a direct link from the RM application list to the
Spark history server entry (thus providing a fix for SPARK-2150).

Note this sort of assumes that the different managers will generate app ids that are
sufficiently different from each other that clashes will not occur.
No, what I mean is the following. Instead of
```
.map { // possibly return null here }.sortBy { // do null check here }
```
We do
```
.flatMap { // return an Option here }.sortBy { // no need to do null check }
```
This means by the end of the flat map the resulting list will automatically filter out everything that returned `None` and only retain the ones that returned `Some(...)`. This cuts down on the size of `logInfo` if exceptions are thrown and we can safely assume that everything in this list are not `null`.