IBX-11780: Integrated ContentPublicationStrategyInterface into ContentFormProcessor publish flow

[bnowak]

🎫 Issue	IBX-11780

Description:

ContentFormProcessor::processPublish() now publishes through ContentPublicationStrategyInterface (ibexa/core) instead of calling ContentService::publishVersion() directly. The strategy chain resolves to the synchronous strategy by default, or to the asynchronous one (ibexa/async-content-publishing) when asynchronous content publishing is enabled.

The strategy returns a ContentPublicationResult whose publishedContent is null on the asynchronous path, therefore:

• the content event payload was replaced with content_type (derived from the draft) — payload consumers are adjusted in the ibexa/dashboard and ibexa/admin-ui counterpart PRs,
• on the asynchronous path the redirect targets are derived from the draft; for never-published content no location exists yet, so the redirect is generated with locationId = null (the proper redirection target for this case is a TODO handled separately).

The synchronous path behaves exactly as before. processPublish() is now covered with unit tests (strategy invocation, payload contract, sync/async redirect matrix, redirectUrlAfterPublish override).

For QA:

• With asynchronous content publishing disabled (default): publishing existing and newly created content from AdminUI behaves as before (redirect to the content/location view).
• With asynchronous content publishing enabled: the publish action returns immediately; publishing an existing item redirects to its location view and the new version goes live once the background job completes.

Documentation:

Part of the IBX-11780 asynchronous content publishing epic — editor-facing behaviour (non-blocking publish) is documented at the epic level; nothing separate to document for this PR.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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