refactor: BREAKING CHANGE remove airbnb deps

[nilzona]

To be able to have a cleaner setup we would let the user choose which of airbnb/airbnb-base that should be decorated. This PR removes unnecessary dependencies and warnings if you want to use the base variant.

So we would let the user install either eslint-config-airbnb or eslint-config-airbnb-base together with the peer dependencies and then the eslint config would be as follows:

module.exports = {
  extends: ['airbnb', 'airbnb-typescript'],
};

or for base

module.exports = {
  extends: ['airbnb-base', 'airbnb-typescript/base'],
};

This fixes #6

[robertsonjoe]

This should be merged in, fixed the issue I was having.

thanks @nilzona

[nilzona]

doesn't seem like this is going to be merged or considered.
@iamturns I turned my fork of this project into a monorepo where both typescript flavors of airbnb and airbnb-base are being released as separate packages. I remember seeing a comment from you that you would like to do that here also. Depending on how you do it, it could be breaking the current airbnb-base users, but the normal airbnb use case would not be breaking. If you want I can submit a PR with that approach instead?