IBX-4629: Implement Meta field groups

[barw4]

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

A new configuration has been implemented that allows configuring fieldgroups that would be shown in the "Meta" section in the content form:

    system:
        admin_group:
            admin_ui_forms:
                content_edit:
                    meta_field_groups_list:
                       - metadata

The default value is set to metadata, however, one can configure it to include any of available fieldgroups or even disable this feature:

    system:
        admin_group:
            admin_ui_forms:
                content_edit:
                    meta_field_groups_list: []

The meta_fieldgroup_list configuration is not deeply merged so overriding it is simple.

Also, a minor bug fix was done in order to scroll to a chosen field via an anchor on the left.

Example:
Using a fresh Ibexa DXP installation and the following meta configuration:

    system:
        admin_group:
            admin_ui_forms:
                content_edit:
                    meta_field_groups_list:
                       - content

with short_name being changed to Metadata fieldgroup, and taxonomy_entry_assignment being set to meta: true, one can observe the following:

One last thing worth mentioning is that meta: true configuration still applies, so we should decide whether to disable it for the taxonomy and the product_catalog packages and allows developers to decide whether to apply it themselves or leave it as it is for now with an annotation in the Developer Documentation.
// Edit - will be removed from both those packages, however, this configuration still is valid.

Short summary, both the meta_field_groups_list and the meta: true configurations are valid.

Related PRs:

• https://github.com/ibexa/taxonomy/pull/177
• https://github.com/ibexa/product-catalog/pull/868

Checklist:

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

[webhdx]

Very good contribution 👍 I have only some small complaints.

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
3.2% Duplication

[micszo]

@barw4 two questions:

1. Is it intended that in Content tab anchor is placed on categories?
   
   When in Meta tab anchor is placed on fields.
   

2. Does this implementation support adding e.g. Basic information category as third tab? Billing address as fourth tab and so on.
   

[barw4]

@micszo

1. I didn't change any behavior here. The fields were visible with meta:true as well before this PR, probably because there would be less of them.

2. No, Meta is hardcoded and we only allow to set specific field groups to it.

[barw4]

@micszo adding to my previous comment, basically, this PR allows us to additionally add field groups to the Meta tab. Previously we allowed only field types, now we allow to put field groups there as well.

[micszo]

QA Approved on Ibexa Commerce 4.3.3-dev.

Encountered an JS issue with subcategory anchors highlighting but managed to reproduce it without these changes. Will be reported separately - update: so far deterministic steps were not found 😞.

Behat tests adjusted here and in https://github.com/ibexa/workflow/pull/70.