Explore how we might support simple tables

## User story

### Form building / Response retrieving
As a **form builder or program administrator**
I want to **include tables as part of my form to collect data in a structured tabular way**
So that **I can process it more easily and reduce cognitive load for end users**

For example: budget tables for grants and contributions

## Context

Integrating simple tables into forms is on the roadmap as an "opportunity on the radar to explore"

GCDS has a table component: https://design-system.canada.ca/en/components/table/

Clients have also asked about this feature in various support tickets:
- https://cds-snc.freshdesk.com/a/tickets/26693
- https://cds-snc.freshdesk.com/a/tickets/29065
- https://cds-snc.freshdesk.com/a/tickets/26405
- https://cds-snc.freshdesk.com/a/tickets/25102
- https://cds-snc.freshdesk.com/a/tickets/28443
- https://cds-snc.freshdesk.com/a/tickets/28788
- https://cds-snc.freshdesk.com/a/tickets/29302
- https://cds-snc.freshdesk.com/a/tickets/27428
- https://cds-snc.freshdesk.com/a/tickets/26693
- https://cds-snc.freshdesk.com/a/tickets/24400

## Acceptance criteria

- [ ] Provides an accessible experience
- [ ] Provides equal service in French and English
- [ ] Provides auto-completion options for fields
- [ ] Provides clear validation feedback and error messages
- [ ] Works in unauthenticated state (signed out) and authenticated (signed in)
- [ ] Works with draft, published, open, closed, archived forms
- [ ] Works with collaboration, versioning,
- [ ] Works with older versions of forms (backwards compatibility)
- [ ] Works with email delivery, API retrieval and HTML/CSV/JSON download
- [ ] Works on Chrome, Firefox, Edge, Safari, and Opera
- [ ] Can be navigated using a screenreader
- [ ] Can be navigated using a keyboard
- [ ] Can be navigated with increased magnification
- [ ] Can be perceived with strong colour contrast
- [ ] Meets a11y testing / WCAG 2.1 AA requirements
- [ ] Meets Protected B level of security, with safeguards in place
- [ ] Mitigates or documents risks involved
- [ ] Collects monitoring data intended, updates to logs and SuperSet if needed
- [ ] Updates to marketing site, guidance pages, API docs, support canned responses, or other documentation

No files, tests, or entry points are named. Start by reviewing the GCDS table component and the linked support tickets, then define the table scope against the listed accessibility, localization, compatibility, security, and delivery requirements; done means an agreed implementation plan and clarified acceptance criteria.

Written by the indexing model from the issue text.