SPARK-2621. Update task InputMetrics incrementally

The patch takes advantage an API provided in Hadoop 2.5 that allows getting accurate data on Hadoop FileSystem bytes read.  It eliminates the old method, which naively accepts the split size as the input bytes.  An impact of this change will be that input metrics go away when using against Hadoop versions earlier thatn 2.5.  I can add this back in, but my opinion is that no metrics are better than inaccurate metrics.

This is difficult to write a test for because we don't usually build against a version of Hadoop that contains the function we need.  I've tested it manually on a pseudo-distributed cluster.

ah I see now - so should we call this function `getThreadLocalBytesRead` or something? It seems like it only semantically makes sense if the returned function is called from the same thread as the function was generated in. That might also be worth documenting in the javadoc. The use of the phrase "so far" there also threw me off a bit - maybe there is a better phrase for that.