Add interface for ContentRichEntityRepository

[alexander-schranz]

We require a minimal interface which all content rich entity need to implemented. This interface should then be used to provide basic implementations of:

• ContentRouteDefaultsProvider
• TeaserProvider
• LinkProvider
• SmartContentProvider
• Selection
• Single Selection

It should also replace the whole DimensionContentRepository which we sadly use at a lot of cases.

[coveralls]

Pull Request Test Coverage Report for Build 10318437173

Details

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 10299929317:	0.0%
Covered Lines:	2532
Relevant Lines:	2532

---

💛 - Coveralls

[alexander-schranz]

@Prokyonn what do you think about the interface?

[alexander-schranz]

this may is a ids or uuids so not sure about how we handle this. Should we go with identifiers @Prokyonn

[alexander-schranz]

The ContentRichEntityInterface has a getId():

SuluContentBundle/Content/Domain/Model/ContentRichEntityInterface.php

Line 26 in f36e36d

public function getId();

but now that we said may Identifier make more sense in case of id vs uuid. But another option is as we already force getId in the interface keep ids and may also just rename Artice:uuid to Article::id even if its a uuid. /cc @chirimoya

[Prokyonn]

Technically speaking, id is just the abbreviation of identifier 😅
also writing ['identifier' => xx] feels more cumbersome than 'id' => xx 🤔

Although we may use uuid, I think I would still go with id as a string.

[alexander-schranz]

ids / identifiers is the only when which need be implemented the other filters are provided via the QueryEnhancer:

            $this->dimensionContentQueryEnhancer->addFilters(
                $queryBuilder,
                'example',
                ExampleDimensionContent::class,
                $filters,
                $sortBys
            );