add optional project row and attachment exports

[andz-bb]

Description

adds optional project data export on top of #19615.

• adds an off-by-default option for rows in included Budibase DB tables and their referenced attachments
• imports fresh row and attachment identities, rebuilds relationships and shows data counts in the existing import summary
• preserves stored values and maps native user references to the importing user
• checks row quotas and rolls back partial writes without running row automations or AI generation

this includes every row in each included table, including shared tables. external database data, screen assets and agent knowledge are outside this change. attachment bytes follow the existing workspace encryption exception; the export dialog explains this when encryption is selected.

covered by data export/import, relationship, attachment, quota and rollback tests. schema-only, encrypted and repeated imports have also been checked manually.

part 6 of the six-part projects stack. review against the preceding branch.

Addresses

• Projects #18349

App Export

• n/a

Screenshots

• n/a

Launchcontrol

optionally includes starter data and row attachments when sharing a project

---

Summary by cubic

Adds an optional rows and attachments export to project packages so recipients can share starter data instead of empty tables. When enabled, every row in each included Budibase DB table, including shared tables, is exported with its referenced attachments. The import result modal now also appears whenever data was imported, even when there are no requirements or unsupported content.

Behavior

• Imports generate fresh row and attachment identities, rebuild relationships, and report data counts in the import result modal.
• Imported rows preserve stored values, continue Auto IDs above imported values, and map native user references to the importing user or reject rows without one.
• Package data and its manifest are validated before import; invalid or duplicate rows, relationships, attachments, and load limits are rejected.
• Row imports are checked against the row quota and rolled back cleanly on failure, without running row automations or AI generation; partial writes and uploaded attachments are removed, while completed imports are preserved if only releasing the assignment lock fails.
• Attachment bytes keep the existing workspace encryption exception, so they are not encrypted even when export encryption is selected; the export dialog warns about this.
• Relationships to rows outside the exported tables are omitted and reported as unsupported content.
• External database data, screen assets, and agent knowledge are outside this change.

Addresses #18349; part 6 of the six-part projects stack.

^{Written for commit d549923. Summary will update on new commits.}

[cubic-dev-ai]

All reported issues were addressed across 14 files

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>