Add command to flag data formatting issues

[fwextensions]

• Add lint npm script.
• Log detailed info for sources with with crosswalk fields that don't appear in their .csv files.
• Add Fuse.js package to search for possible matches of missing fields.
• Check for JSON appearing in .csv files.
• Add support for custom ogr2ogr command in .env file, to handle Windows usage.
• Update README.md with Windows install info.
• Fix "numberic" and other typos.
• Remove the double format in identity-source.js.

Running npm run download and then npm run lint will check the crosswalk fields specified in each source against its downloaded .csv file. Fields that aren't found in the header row of the file are listed, along with any column names that are similar. Example output for Escondido:

    escondido
        C:\path\to\repo\wtt_area\data\raw\escondido.csv
        ref: TREEID
        scientific: BOTANICAL => Maybe: BOTANICAL_NAME
        common: COMMON => Maybe: COMMON_NAME
        height: Height => Maybe: HEIGHT_RANGE, ACTUALHEIGHT
        health: CONDITION => Maybe: TREE_CONDITION

#20 and #21 should be merged before this PR.

[zoobot]

Here's code conventions for this project.
Please separate different issues into separate PRs if you want contributions reviewed and merged, thanks.
This looks like it can be broken up into 3-5 different PRs.

[zoobot]

@fwextensions Mind if I branch off this and break it up into multiple PRs?
I want to have linting separate from custom ogr2ogr and source formatting.

[fwextensions]

Making ogr work on Windows is just a few lines of code, but feel free.