IBX-2667: Added Content Type Meta anchor menu

[ciastektk]

Question	Answer
Tickets	https://issues.ibexa.co/browse/IBX-2667
Bug fix?	no
New feature?	no
BC breaks?	no
Tests pass?	yes
Doc needed?	yes
License	GPL-2.0

Related to:
https://github.com/ibexa/seo/pull/5
https://github.com/ibexa/seo/pull/6
https://github.com/ibexa/seo/pull/11

This PR adds modifications to Field Types management in Content Type create / edit. Field Types which provides more complex functionality like SEO, Taxonomy, should be separated from Field definitions section. Field Types marked as meta Field Type will be presented in anchor menu as regular menu item. Configuration form is rendered below Field definitions section. Meta Field Types contains dynamically added enabled field to configure if Field Type will be used in Content Type or not. Enabling Field Type behave similar to dragging and dropping regular Field Type. Apart of the visual changes, rest of functionally is not changed.

Below configurations allows to configure meta fieldtype for content type:

ibexa:
    system:
        admin_group:
            admin_ui_forms:
                content_type_edit:
                    field_types:
                        ibexa_seo: 	# fieldtype identifier
                            meta: true 	# separate this fieldtype from Field definition section, put it in anchor menu and add enabled field
                            position: 100  # display meta field type on proper position in menu and content  

To use meta Field Types from anchor menu, meta field definitions must be added to ContentTypeDraft or ContentTypeCreateStruct before form will be rendered. ContentTypeController::addMetaFieldDefinitions is responsible to do that. In create action new meta field definitions are created for all configured meta Field Types. In edit action new meta field definitions are created for all configured and not enabled meta Field Types. Field Definitions for enabled Field Types are taken from database.

Before ContentType will be updated meta Field Definitions for all not enabled Field Types are removed.

Checklist:

• Coding standards ($ composer fix-cs)
• Ready for Code Review

[webhdx]

I see ContentTypeEditAnchorMenuBuilder is made after #526 but this menu has different structure according to the mockups. It has to be fixed once the frontend part is done.

[alongosz]

I feel like whether a Field Definition is meta or not should belong to Core API, not Admin UI. However probably coming a bit too late to the party, so here are the remarks for the current solution:

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

No Coverage information
2.4% Duplication

[micszo]

QA Approved on 4.2.2-dev.

Tested with all editions.