IBX-12039: Migrated versions tab tables to ibexa.Table component

[ciastektk]

⚠️ Remove temp commit

Revert 2d7d50dd0 ([CI] Added temporary dev dependency on ibexa/twig-components) before merge.

🎫 Issue	IBX-12039

Related PRs:

• IBX-12039: Added table component extension api twig-components#29 (required, see dependencies.json)
• https://github.com/ibexa/workflow/pull/190
• https://github.com/ibexa/translations-management/pull/152

Description:

Rework of this PR after review feedback (thanks @ViniTou): instead of introducing a versions-specific column-provider mechanism, the Versions tab tables are migrated to the ibexa.Table TwigComponent — the same extension point already used by product-catalog and connector-quable. Any package contributes a column with a plain PostMountEvent subscriber; no second mechanism, no new public contracts.

• VersionsTableSubscriber provides the core columns (checkbox, version, modified language, contributor, created, last saved, actions) from content/tab/versions/columns.html.twig blocks. Priorities 110–90 / 40–10; the 50–89 band is reserved for third-party columns.
• All four render sites now mount the component: draft / published / archived tables in tab.html.twig and the draft-conflict modal. Forms, bulk-delete header tools, Pagerfanta pagination and the admin-ui-versions-table-before component group are preserved.
• The headline is rendered through the component (headline prop), so subscribers may replace it (ibexa/workflow restores its "Drafts to review" headline this way).
• The provider mechanism from the previous iteration of this PR is gone — it was never released, so there is no BC impact from removing it.

For QA:

On a content item with drafts, published and archived versions verify: bulk delete of drafts/archived (select-all, trash button enable, confirmation modal, POST to ibexa.version.remove), drafts pagination (page param + #ibexa-tab-location-view-versions fragment), draft-conflict modal table (no checkbox column, no "Created" column), per-row actions menu, archived restore. With ibexa/workflow enabled: "Workflow" column + "Drafts to review" headline on the drafts table for content in a workflow. With translations-management: "Translation status" column on drafts of auto-translated content.

Documentation:

Template BC break — content/tab/versions/table.html.twig is removed, together with its override blocks (custom_column_headers, custom_actions_column_headers, custom_columns, custom_actions_column) and the table_template_path variable. Projects that overrode this template or those blocks must migrate to a PostMountEvent subscriber adding a column to the ibexa.Table component (guard on Table::$type === 'versions'; see VersionsTableSubscriber and the workflow/TM subscribers as references). Needs an upgrade note on doc.ibexa.co.

[ViniTou]

Not going into details, but isnt this case covered by
ibexa/twig-components#25
?

[bnowak]

looks good 💪 More likely, I'll reuse that part in async content publishing :)

don't forget to remove dependencies.json before merging 😉

[bnowak]

What is that value, priority/order? we could left some comment at least here 😉

as well as below

[ciastektk]

Fixed: 297421f

[mnocon]

Hi! When talking with @Steveb-p about ibexa/twig-components#25 (ibexa/twig-components#25 (comment) , discussed on Quable daily ), the Table component was meant to be internal for now.

Given this, do you still think it needs to be mentioned in the doc somehow?

[ciastektk]

Hi! When talking with @Steveb-p about ibexa/twig-components#25 (ibexa/twig-components#25 (comment) , discussed on Quable daily ), the Table component was meant to be internal for now.

Given this, do you still think it needs to be mentioned in the doc somehow?

Hi! If there is some reasons that ibexa.Table component should be internal then IMO we should still not mention this component in the doc.

[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

[Steveb-p]

Hi! When talking with @Steveb-p about ibexa/twig-components#25 (ibexa/twig-components#25 (comment) , discussed on Quable daily ), the Table component was meant to be internal for now.
Given this, do you still think it needs to be mentioned in the doc somehow?

Hi! If there is some reasons that ibexa.Table component should be internal then IMO we should still not mention this component in the doc.

It is not intended for external use. At least not yet. Experimental at best.