Component lists rewamp

### Describe the problem

Presently, component lists are a site-wide grouping of components across projects, configurable in the Django admin only.

The original intention was to be able to see progress of translations across projects.

A typical use case is openSUSE, which uses these to track translation progress of individual distro releases: https://l10n.opensuse.org/component-list/opensuse-leap-15_6/

### Describe the solution you would like

We need to better define expectations and then adjust implementation.

* What do we expect from component lists? Especially on shared sites, where there is no need for centralized component lists.
* Who should be able to create and edit component lists? This is bound to the previous question.
* Should it affect permissions? It currently does and complicates the code.

### Describe alternatives you have considered

_No response_

### Screenshots

_No response_

### Additional context

* [ ] https://github.com/WeblateOrg/weblate/issues/1370
* [ ] https://github.com/WeblateOrg/weblate/issues/7181
* [ ] https://github.com/WeblateOrg/weblate/issues/11549
* [ ] https://github.com/WeblateOrg/weblate/issues/5792
* [ ] https://github.com/WeblateOrg/weblate/issues/14663
* [ ] https://github.com/WeblateOrg/weblate/issues/18215