IBX-10527: Content type search API

[barw4]

🎫 Issue	IBX-10527

Related PRs:

ibexa/core#633

Description:

The new route is exposed at /api/ibexa/v2/content/types/view [POST] and accepts the following payload:

{
    "ViewInput": {
        "identifier": "ContentTypeView",
        "ContentTypeQuery": {
            "limit": "1",
            "offset": "0",
            "Query": {
                "ContentTypeIdCriterion": [1,2],
                "ContentTypeIdentifierCriterion": "folder",
                "IsSystemCriterion": true,
                "ContentTypeGroupIdCriterion": 1,
                "ContainsFieldDefinitionIdCriterion": 2
            },
            "SortClauses": {
                "Identifier": "descending",
                "Id": "ascending"
            }
        }
    }
}

with the following headers:
ContentType -> application/vnd.ibexa.api.ContentTypeViewInput+json
Accept => application/vnd.ibexa.api.ContentTypeView+json

For QA:

Documentation:

[Steveb-p]

This should be placed on top of the file, directly under services key - as this affects all services in this file.

Also note that this does not mean ContentTypeCriterionInterface parsers will be automatically tagged. It only means that services declared in this file that are instances of that will be tagged. You need Container::registerForAutoconfiguration() in extension instead for this to happen.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud