Factor in 'raw' configurations on top of 'reported' ones

[JoshuaKGoldberg]

PR Checklist

• Addresses an existing issue: fixes Missing extends in generated config #232
• That issue was marked as status: accepting prs

Overview

Before this change, find*Configuration functions for linters only returned the 'reported' config, meaning the CLI output of --print-config or similar. This change makes them return two things:

• full: that reported configuration, considered to be the complete list of all original settings
• raw: the naive results of importing the configuration file

The raw config is used to override some settings in the printed output, namely globals and extends, because ESLint prints way too many globals but none of the extends (#232).

A few tangential changes:

• A new importer was necessary for importing .json files with comments.
• Added root object key sorting to the output formatters, since they were getting a little oddly sorted from the raw overrides
• Enabled esModuleInterop in tsconfig.json because strip-json-comments' types don't have a default export

Still to do:

• Flesh out test coverage, especially for the new importer
• Add some JSDoc comments around the more confusing areas... perhaps a .md addition?
• Double-check this works locally (initial runs worked well!)

[jeremyyap]

Hi @JoshuaKGoldberg I noticed TSLint rule arguments are not being picked up in the latest release and I think the issue might be here. Should this be reportedConfiguration instead?

[JoshuaKGoldberg]

Perhaps! @jeremyyap would you mind filing an issue! I can take a look later today.