Feat - Add configurable table question type

[RomainLvr]

Checklist before requesting a review

Please delete options that are not relevant.

• I have performed a self-review of my code.
• I have added tests (when available) that prove my fix is effective or that my feature works.
• I have updated the CHANGELOG with a short functional description of the fix or new feature.
• This change requires a documentation update.

Description

• It fixes !43740
• Here is a brief description of what this PR does

Adds a new Table question type to the plugin, letting form
designers collect tabular data with fully configurable columns.

Changes

• Configurable columns: each column has a label, a cell type (reusing a compatible core question type), an optional item type, and a "required" flag.
• Configurable rows: min/max row count, with end users adding/removing rows dynamically.
• End-user input: renders an editable table; select-based cells (users, items, devices…) use select2.
• Answer display: stored answers are rendered back as a clean read-only table.
• Required-column validation:
  • Server-side (authoritative) via QuestionTypeValidationInterface — blocks submission when a filled row leaves a required cell empty.
  • Client-side — highlights only the offending cells (red border + message) and blocks the submit before the server round-trip.
• Disabled by default; enabled from the plugin configuration like the other advanced question types.

Tests

• Unit + integration tests for config (de)serialization, compatible types, cell rendering, editor/helpdesk rendering, and required-column validation across every compatible column type.

Screenshots (if appropriate):

Fill form exemple :

[RomainLvr]

@ccailly suggested making the column limit a validation criterion (like those already present in Forms) rather than managing it manually. The benefits would be:

• Easier and more robust
• Useful in other situations to have this new criterion