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/n8n-node/nodes/Probo/actions/index.ts

@@ -25,6 +25,7 @@ import * as meeting from './meeting';
 import * as organization from './organization';
 import * as user from './user';
 import * as risk from './risk';
+import * as statementOfApplicability from './statementOfApplicability';
 import * as vendor from './vendor';
 
 export interface ResourceModule {
@@ -50,6 +51,7 @@ export const resources: Record<string, ResourceModule> = {
 	organization: organization as ResourceModule,
 	user: user as ResourceModule,
 	risk: risk as ResourceModule,
+	statementOfApplicability: statementOfApplicability as ResourceModule,
 	vendor: vendor as ResourceModule,
 };