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
I started thinking about how to use heading properly within HTML code. There are 2 approaches that might work for us. 
The first one is based on HTML5 semantic structure which allows developers to define many `<h1/>` elements inside the HTML code of page. The priority of headings depends on content structure/nesting level. So in the case above, it would be `<h1 class="ez-contenttypeselector-title"/>`, then later in the code we will have `<h2 class="ez-contenttypeselector-zone-title"/>`.
The second approach is to use `<h3/>` headings for modules which are not describing the content itself. In such a situation we will have `<h3 class="ez-contenttypeselector-title"/>`, then `<h4 class="ez-contenttypeselector-zone-title"/>`.
What do you think about these approaches?