Store overhaul (#142)

* feat: small library tweaks + company page

* feat: new store view

* fix: ci merge error

* feat: add genres to store page

* feat: sorting

* feat: lock game/version imports while their tasks are running

* feat: feature games

* feat: tag based filtering

* fix: make tags alphabetical

* refactor: move a bunch of i18n to common

* feat: add localizations for everything

* fix: title description on panel

* fix: feature carousel text

* fix: i18n footer strings

* feat: add tag page

* fix: develop merge

* feat: offline games support (don't error out if provider throws)

* feat: tag management

* feat: show library next to game import + small fixes

* feat: most of the company and tag managers

* feat: company text field editing

* fix: small fixes + tsgo experiemental

* feat: upload icon and banner

* feat: store infinite scrolling and bulk import mode

* fix: lint

* fix: add drop-base to prettier ignore

CONTRIBUTING.md

@@ -148,7 +148,6 @@ type(scope)!: subject
 ```
 
 - `type`: the type of the commit is one of the following:
-
   - `feat`: new features.
   - `fix`: bug fixes.
   - `docs`: documentation changes.
@@ -165,7 +164,6 @@ type(scope)!: subject
 - `scope`: section of the codebase that the commit makes changes to. If it makes changes to
   many sections, or if no section in particular is modified, leave blank without the parentheses.
   Examples:
-
   - Commit that changes the `git` plugin:
 
   ```
@@ -179,7 +177,6 @@ type(scope)!: subject
   ```
 
   For changes to plugins or themes, the scope should be the plugin or theme name:
-
   - ✅ `fix(agnoster): commit subject`
   - ❌ `fix(theme/agnoster): commit subject`
 
@@ -209,7 +206,6 @@ type(scope)!: subject
   to specify other details, you can use the commit body, but it won't be visible.
 
   Formatting tricks: the commit subject may contain:
-
   - Links to related issues or PRs by writing `#issue`. This will be highlighted by the changelog tool:
 
     ```