IBX-6282: Added attributes support for generating name schema

[kisztof]

Question	Answer
JIRA issue	IBX-6282
Type	improvement
Target Ibexa version	v4.6
BC breaks	no

This PR added significant changes to content naming in the system, introducing custom name schemas using attributes. The name schema pattern used in these events matches the URL Alias schema pattern for consistency.

Added two new events:

• \Ibexa\Contracts\Core\Event\NameSchema\ResolveNameSchemaEvent and \Ibexa\Contracts\Core\Event\NameSchema\ResolveContentNameSchemaEvent, enabling dynamic name schemas for content.

Refactored names:

• resolve() => resolveNameSchema()
• resolveNameSchema() => resolveContentNameSchema()

Checklist:

• Provided PR description.
• Tested the solution manually.
• Provided automated test coverage.
• Checked that the target branch is set correctly (main for features, the oldest supported for bugs).
• Ran PHP CS Fixer for new PHP code (use $ composer fix-cs).
• Asked for a review (ping @ibexa/engineering).

[konradoboza]

Also, this this remark hasn't been incorporated: https://github.com/ibexa/core/pull/257/files#r1304080695.

[micszo]

Publishing product with name pattern <name>-<attribute:battery_type>-<attribute:disk_size> causes error:

Ibexa\ProductCatalog\Event\NameSchemaSubscriber::getProductSpecificationFieldFromEvent(): Return value must be of type ?Ibexa\ProductCatalog\FieldType\ProductSpecification\Value, array returned

[micszo]

With this change content name pattern is ignored when different URL alias name pattern is provided:

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
0.0% Duplication

[micszo]

Using attributes in product name pattern works fine now.
Previous issues have been resolved.

QA Approved on Ibexa Commerce 4.6.x-dev.