Use different csv parser

Changed the csv parser from fast-csv to a more popular node-csv parser. This parser had an admittedly undocumented relaxed parsing mode that made it more resilient to some csv formatting issues. Without the relaxed mode turned on, it would error out on the WI feed I'm testing with, and would give line numbers, but the line numbers didn't correspond to any lines that had actual problems. So turning on the relaxed mode seemed better, and allowed it to process an unadulterated feed.

I also had to try turning on a mongoose aggregate mode that allows it to use disk for some processing, otherwise the unique id check was too large to hold in mongo's memory.

Assigning to @cap10morgan 
So, some of this is conjecture here, but one requirement of the v3.0 VIP spec is that every ID is unique for every element of the feed. In the WI feed street segments alone, there are almost 2 million records, so add to that all the other elements and round up and we'll call it 2 million. So this checker is looking at the ids for all 2 million documents, and looking for duplicated ids. My guess is that some (hopefully subset) of all 2 million documents gets loaded into memory for matching and duplicate detection. When I ran without this feature turned on, I basically got an error message that suggested this option as a fix, and after applying it I got past this hurdle. Some info can be found here: http://docs.mongodb.org/manual/core/aggregation-pipeline-limits/#agg-memory-restrictions