Changes to the `recommended` config

[JasonWeinzierl]

Since the recommended config was last updated in 2021, a few rules were improved or added. I'd like to add the following to the recommended config:

• prefer-observer
  • Had a fixer added
  • RxJS has since deprecated passing separate callback arguments
• throw-error
  • Narrowed to just the throwError function instead of regular JavaScript throw feat(throw-error)!: stop linting throw statements #22
• prefer-root-operators feat(prefer-root-operators): new rule #34
  • Adding this rule would also require bumping the RxJS peer dependency from v7.0 to v7.2.
• no-topromise
  • RxJS has deprecated this method
  • Rule has been enhanced with editor suggestions feat(no-topromise): suggest lastValueFrom or firstValueFrom #38

Additionally:

• Change no-implicit-any-catch's allowExplicitAny to true in the recommended config in the rule's defaults.
  • It currently defaults to false. However, other rules in this plugin allow any by default, so this is inconsistent.
  • More lax codebases tend to turn this option on because they haven't banned explicit any completely.
  • We should enforce banning any more consistently in the proposed strict config: Introduce a strict config #36

Feedback is welcome.