Preset for Type-Aware rules #445
Description
Is your feature request related to a problem? Please describe.
In the latest iteration (v6.4.1) useAwaitThenable has been added into core rules. In the official documentation this rule is listed under the project domain. So it will end up causing slowness to prevent which other Scanner based rules have been turned off by default in the config.
Describe the solution you'd like
I am not asking for outright removal of this rule, since I personally regard this, and other type-aware rules (Scanner rules that come from @typescript-eslint like noFloatingPromises, noDeprecated imports) as valuable even though they come at a performance cost. Alternatively I suggest addition of another preset for type-aware rules, which can be "opt-in" by nature, possibly through a query (that highlights the tradeoffs as well) after the framework selection phase when init command is run. Maybe instead of just type-aware rules it could extend to useful scanner rules in general, I don't have a preference on the route taken
Describe alternatives you've considered
Currently I just enable the scanner rules that I deem necessary in my configs, so its no big issue if this request is rejected regardless, but it would nice to have a preset for someone wanting to setup from zero, who has not been through what each rule does.