EZP-23536: As a developper, I want to refactor/fix content type list related views

JIRA: https://jira.ez.no/browse/EZP-23536

# Description

The main point here was to improve the content type list related to so that the code is better architecture with less code duplication and each component has one responsibility.

Screencast: https://www.youtube.com/watch?v=xFJzW4-G1Jo

In details:

* get rid of the *create content filter view* that duplicated a lots of code and was doing to many things
* added a *content type selector* that decorates a *selection filter view* to allow the filtering by content type groups
* improved the *selection filter view* so that the source can be an array of objects (only string was supported before)
* added a *loading* indicator so that the user is informed that something is happening behind the scene
* make sure the types list is sorted alphabetically
* make sure there's always at least a content type group selected
* make sure the 'Content' group is selected by default
* improved the CSS styles to be consistent with the content tree and for a better information organization on that area

## Limitations, known issues

* [EZP-23696](https://jira.ez.no/browse/EZP-23696): the full list of content types is always presented, it's not filtered with the user's policy
* [EZP-23429](https://jira.ez.no/browse/EZP-23429): the name of the content type is always the name in eng-GB (even if the content type is not translated in this language...)

# Tests

unit tests + manual tests
For now we use more or less the first one and actually this module describes the "content ifself" as it (will) basically list(s) the content types the user is allowed to choose to create a sub-item. It's an h2 because it's at the same level as the raw content view for instance. I always see the heading level as a way to build a table of content, so here we can represent the location view in the following way

The content display it self at the top (h1) "containing":
  * The raw content view (h2 "Contents")
  * At some point the meta data (h2 "Metadata" for instance) 
  * The list of content type you can create (h2 "Choose a content type")
  * in the future, the sub-items list (so with a h2 like "Sub-items")
      * each sub item might be displayed (so with a h3 if we need a heading)