Separate base rules from Node-specific rules and add TypeScript rules

[Maximization]

Goal is to have three different configs available for end users:

• async - base framework-agnostic rules
• async/node - additional rules for Node.js
• async/ts - specific rules for TypeScript users

Similar to how eslint-config-hardcore does it. Then folks can choose to use some (or all) of the rules in their projects based on the type of project they're working in.

{
  "extends": [
    "async",
    "async/node",
    "async/ts"
  ]
}

Give this a thumbs up if you want to see it implemented.

[Maximization]

Solved with the release of 2.0.0