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.
@tgravescs sorry, I see what you mean now. Still, I see this as an improvement; the `scheduler` variables in all the cases are not used anywhere - in fact, even the `initialize` calls are duplicated in all the different cases.

So unless there is a real desire to be able to match backends and schedulers at will, I think encapsulating the backend initialization like I did is a better pattern.