Consider merging with `@types/chrome`

Have you considered merging this project with `@types/chrome` and using the `@types/chrome` NPM name going forward? Two benefits:

- No confusion around "what's the right package to use"
- TypeScript has some special handling for the `@types` node_modules folder which it will import automatically. This is perfect for a package like this (similar to `@types/node`) which also contains global type definitions. This means a user can just `yarn add -D @types/chrome` and doesn't have to change their `tsconfig.json`.