google-chrome: move independently of `chromium`

Historically, `google-chrome` used the version info and debian package
FOD provided by `chromium`.

This was very efficient, because `chromium` uses parts of the debian
tarball for Widevine (opt-in, via `.override`).

Meaning `chromium` has to track that debian tarball with each update
anyway.

And they always release in sync.

So why keep seperate `google-chrome` from `chromium` now?

 - The current `chromium` maintainers are already at capacity
   maintaining `chromium` and have no time for `google-chrome`.

 - `chromium` bumps become sometimes a bottleneck for `google-chrome`.
   This is because `chromium` is built from source and a lot more time
   consuming and significantly more complex.

 - Lately, `chromium` and `google-chrome` both had an upstream issue
   under wayland with `--ozone-platform-hint`, rendering it unusable.
   For `chromium` we were able to patch it, since unlike `google-chrome`
   it's built from source.
   The `chromium` maintainers simply forgot that `google-chrome` might
   have the same issue, continued to merge the PR, rendering
   `google-chrome` broken.

This PR also removes primeos from `meta.maintainers` since they only
added themself to `google-chrome` because it inherited `chromium`'s
version, stating they don't actually use `google-chrome`.

Furthermore, primeos no longer maintains `chromium`.
Ref 477e7d6b60e817661632ff3a8aaf2e39c4cceadc

(cherry picked from commit 9f96faf9d8d5ba69f1772d087284bb6d2a67f356)

0 files changed, 0 insertions, 0 deletions