Add name parsing libraries for scientific name-based taxonomic units

[gaurav]

Currently, we use simple regular expressions to do this, but something like TaxaMatch would be better. There should also be a clear visual indicator to indicate that a name couldn't be parsed.

[hlapp]

We might want to distinguish between name parsing and name matching. gnparser will probably work very well for the former. It sounds though that what you're really talking about here is matching, despite the title?

[gaurav]

This issue (#14) covers name parsing, while #15 covers name matching/resolution. At the moment, we parse names with pretty simple regular expressions, so TaxaMatch or gnparser would be a step up from that and would be able to handle much more complicated names.

However, maybe we don't need anything that advanced just yet, while comparing our names to taxonomic authorities would immediately highlight typos and other resolution errors. I wanted to file them separately so we could prioritize them separately.

[gaurav]

Name parsing should take place in phyx.js, so I've created an issue to cover that at phyloref/phyx.js#7. Displaying and editing the results of the parsing is covered by #16. The Curation Tool should really not be doing any name parsing at all, although it should support looking up names and specimens on biodiversity databases (#15). I therefore think we should close this issue.