Create a map from Neataptic's import / export system to Carrot

[christianechevarria]

Is your feature request related to a problem? Please describe.
In #152 @tracycollins was experiencing bugs trying to import directly from Neataptic because the import / export system has changed throughout the development of Carrot

Describe the solution you'd like
A function that maps the JSON output from Neataptic's export into Carrot's import JSON format

Getting this done would just require a couple steps:

• Note the differences in structure between Neataptics export and Carrot's export / import
• Write a function that traverses neataptic JSON keys and maps them to Carrot's expected structure
• Document the map in the README or documentation for future users making the migration
• Bonus: Consider the ideal JSON import / export system agnostic to JS library to make future interoperability seamless

Update: We're currently in the middle of a substantial overhaul of the library to accommodate the full neat algorithm on the full-neat branch and we're not sure what the final to / from JSON system is going to look like once we complete those changes. For now, we're thinking it would be best to write the conversion code once we can pin down the (probably) new import / export system to avoid having two separate maps