2.1.0

• Removed issue templates since all they did was to increase noise.
• Beg for detailed bug reports (please for the love of all that's holy, add some information in your bug reports)
• Better handle improper config files and distinguish "unhandled errors" in the plugin from "parse failures" of .editorconfig and .jsbeautifyrc files
• Handle all OS errors as potentially node.js not being found. The existing approach in the new v2.0 was trying to identify which OS errors were actually about node.js paths being improperly set, but it seems like this isn't enough for all users (e.g. chinese). Give up and treat unknown OS errors as also potentially being about node.js paths, which seems generally true