Linting pkg json

[brettz9]

Ok, one more batch of build/maintenance changes. The significant one is the husky/lint-staged addition to try to ensure that no linting regressions can even be committed, and that there are no test regressions on push. I added some "lite" npm scripts which avoid the benchmarking tests (to avoid running benchmarking on push).

If you are not comfortable with the eslint auto-fixes, I can change so that it just warns us (before commit) to fix it ourselves. But with the eslint rules you have enabled (and without third party eslint plugins, etc.), I think the fixes should be pretty safe and conveniently address accidental tab or indent issues.

• Build: Add trailing line-breaks to built JSON/JSON6 (auto-added by IDE settings; otherwise "no newline" willl show in diffs, etc.)
• Linting: Fixes
• Linting: Avoid tabs in json6 file
• Build: alphabetize package.json devDeps (these are also auto-ordered if saving to package.json) and remove duplicate rollup in source package.json6
• Maintenance: .editorconfig fix for JSON/YML
• npm: Add husky and lint-staged
• npm: Add --cache to eslint
• Testing: Bump thresholds to current support (just branches not yet at 100)
• Testing: Add test for incomplete string streamed key in chunks
• Git: Add .eslintcache to ignore file (to avoid adding lint-staged's recommended use of eslint --cache)

[brettz9]

Also, per https://lgtm.com/projects/g/d3x0r/JSON6/?mode=list , throwEndError is passing arguments that don't exist in the function definition (actually it is commented out). Would you like me to remove those extra arguments, use the currently unused variable in some way, or enable it to avoid the linting errors, and instead disable linting errors for no unused variables (i.e., if I enable the currently commented out c argument, the linters will start complaining about this variable being unused unless I suppress that particular error).