[SPARK-4028][Streaming] ReceivedBlockHandler interface to abstract the functionality of storage of received data

As part of the initiative to prevent data loss on streaming driver failure, this JIRA tracks the subtask of implementing a ReceivedBlockHandler, that abstracts the functionality of storage of received data blocks. The default implementation will maintain the current behavior of storing the data into BlockManager. The optional implementation will store the data to both BlockManager as well as a write ahead log.

For these types of "unexpected case" errors, I find it helpful to log the name of the unexpected object's class, e.g.

```scala
case o =>
  throw new SparkException(s"... unexpected block type ${o.getClass.getName}")
```