SOA as document: replace export with publish workflow

Statements of Applicability are no longer exported as one-off PDFs.
Instead, each SOA owns a persistent document that accumulates versions
over time, following the same publish/approve lifecycle as authored
documents.

Publishing without approvers publishes immediately; publishing with
approvers creates a draft pending approval via the existing quorum
system. SOAs can also store default approvers that are pre-populated in
the publish dialog.

The SOA is removed from the snapshot system — applicability statements
are now queried directly (snapshot_id IS NULL) rather than through
snapshot copies.

A standalone migration script (cmd/migrate-soa-snapshots-to-documents)
converts existing SOA snapshots into documents with proper ProseMirror
content, preserving version history and approval decisions.

Signed-off-by: Sacha Al Himdani <sacha@getprobo.com>

packages/ui/src/RichEditor/RichEditor.tsx

@@ -67,7 +67,7 @@ const extensions = [
 ];
 
 const richEditorVariants = tv({
-  base: ["relative flex-1 py-14 pr-8 bg-level-1 shadow-base"],
+  base: ["relative flex-1 min-w-0 overflow-auto py-14 pr-8 bg-level-1 shadow-base"],
   variants: {
     disabled: {
       true: "pl-8",

packages/ui/src/rich-editor.css

@@ -59,7 +59,7 @@
     }
 
     table {
-        @apply border border-border-mid border-collapse;
+        @apply border border-border-mid border-collapse w-max;
         tbody {
             @apply border border-border-mid border-collapse;
         }
@@ -85,7 +85,7 @@
     }
 
     .tableWrapper {
-        @apply relative overflow-x-auto my-4;
+        @apply relative overflow-auto my-4 max-h-[70vh];
     }
 
     .mermaid-block {