[BUG] Separate ESLint settings for ui, content, and background

[tombeckenham]

Describe the Bug

The same ESlint settings have been used across all three areas of the extension. This allows code to be mixed that shouldn't, applies some rules to the background that shouldn't (like hooks), and prevents usage of window on ui.

Expected experience

ESlint should prevent the ui from directly including code from background services, and vice versa. Rules of hooks should only apply to the popup. Globals should be allowed in the popup

Steps To Reproduce

1. Include a file from backround in the UI - eslint doesn't complain and it should
2. Try creating a function starting with "use" in the backgrond - eslint complains when it shouldn't
3. Try using the window global in the popup - eslint complains when it shouldn't

Environment

- OS: Mac
- Node:
- npm: