BUG: Check for NaN after data conversion to numeric
In an attempt to squash a Python parser bug in which weirdly-formed floats weren't being checked for `nan`, the bug was traced back to a bug in the `maybe_convert_numeric` function of `pandas/src/inference.pyx`.  Added tests for the bug in `test_lib.py` and adjusted the original `nan` tests in `na_values.py` to test all of the engines.

## [Current coverage](https://codecov.io/gh/pydata/pandas/pull/13314?src=pr) is **84.22%**

> Merging [#13314](https://codecov.io/gh/pydata/pandas/pull/13314?src=pr) into [master](https://codecov.io/gh/pydata/pandas/branch/master?src=pr) will not change coverage

``` diff
@@             master     #13314   diff @@
==========================================
  Files           138        138          
  Lines         50667      50667          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits          42672      42672          
  Misses         7995       7995          
  Partials          0          0          
```

> Powered by [Codecov](https://codecov.io?src=pr). Last updated by [70be8a9...9e17995](https://codecov.io/gh/pydata/pandas/compare/70be8a95ebeb638aa53f465ba885a7b33b6c35d9...9e17995b67c9c1aa86a31803ad799154e78f2977)
 I suspect `tools/tests/test_util.py` for `to_numeric` might also be affected, can you add a test there as well?

Can you run related perf tests just to see if any effect.
 No need I think: `to_numeric` doesn't pass in any `NaN` values to the funxtion so this branch  has no effect.
 Ran perf tests on  windows and didn't see any noticeable changes
 @jreback : Made the requested changes, and Travis is giving the green light.   Ready to merge if there are no other concerns.
