Migrate `jsonc-parser` to `strip-json-comments`

[kricsleo]

Describe the feature

• strip-json-comments is more lightweight: 559B(gzip) vs 6.7KB(gzip) of jsonc-parser. Yes! Smaller bundle! 🥰
• strip-json-comments is slightly faster. (Performance varies with different JSON content sizes. So this might not be the main consideration)

  strip-json-comments/parseJSONC
   1.15x faster than microsoft/node-jsonc-parser

• strip-json-comments is also widely used (68,837,155 downloads/week, three times of jsonc-parser. Also this isn't the main consideration.)

Downsides:

strip-json-comments is less tolerant than jsonc-parser and may encounter issues with certain edge cases: sindresorhus/strip-json-comments#51

Additional information

• Would you be willing to help implement this feature?

[LukasParke]

I don't think this is a step in the right direction, there is another thread talking about swapping to yaml over js-yaml for better spec compliance over performance, and the AST experience. IMO sticking with a good AST solution that is comment aware is a better idea that just removing all of that context.

Packages using this tool may want to use context in those comments for things like rule ignoring or capturing comments for one purpose or another.