[SPARK-1768] History server enhancements.

Two improvements to the history server:

- Separate the HTTP handling from history fetching, so that it's easy to add
  new backends later (thinking about SPARK-1537 in the long run)

- Avoid loading all UIs in memory. Do lazy loading instead, keeping a few in
  memory for faster access. This allows the app limit to go away, since holding
  just the listing in memory shouldn't be too expensive unless the user has millions
  of completed apps in the history (at which point I'd expect other issues to arise
  aside from history server memory usage, such as FileSystem.listStatus()
  starting to become ridiculously expensive).

I also fixed a few minor things along the way which aren't really worth mentioning.
I also removed the app's log path from the UI since that information may not even
exist depending on which backend is used (even though there is only one now).
The amount of duplicate code is actually minimal (3 lines), and I think it is worth having it in exchange for simpler method signatures. It's fine to keep it as is. This is not a huge deal anyway.

(This is tangential to our discussion, but the reason SparkUI takes in a ListenerBus is because it must listen for events from some source. For live SparkUIs, it listens for live events issued by the DAGScheduler, and for dead SparkUIs, it listens for replayed events from logs. If SparkUI has a method called `replayLogs` or something, then it will have undefined consequences for a live SparkUI.)