fix(company-profile): replace :param::jsonb with CAST(:param AS JSONB)

SQLAlchemy's text() parser treats `:name::jsonb` ambiguously when the
trailing `::jsonb` follows immediately — psycopg2 receives the literal
`:name::jsonb` string and raises a SyntaxError because `:` isn't a
psycopg2 placeholder syntax.

The fix uses ANSI CAST(:name AS JSONB) which is semantically identical
in PostgreSQL but lets SQLAlchemy unambiguously substitute the
parameter.

Effects: PATCH and POST/upsert on /api/v1/company-profile now actually
update the row. Before this fix both endpoints returned 500 (or 200
with stale data) and never persisted edits.

Files touched:
  - _company_profile_sql.py (build_upsert_params / execute_update /
    execute_insert): 12 JSONB columns
  - company_profile_service.py: PATCH dynamic JSONB column,
    audit log insert

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

backend-compliance/compliance/services/company_profile_service.py

@@ -146,7 +146,7 @@ def log_audit(
             text(
                 "INSERT INTO compliance_company_profile_audit "
                 "(tenant_id, project_id, action, changed_fields, changed_by) "
-                "VALUES (:tenant_id, :project_id, :action, :fields::jsonb, :changed_by)"
+                "VALUES (:tenant_id, :project_id, :action, CAST(:fields AS JSONB), :changed_by)"
             ),
             {
                 "tenant_id": tenant_id,
@@ -318,7 +318,7 @@ class CompanyProfileService:
                 continue
             param_name = f"p_{key}"
             if key in _JSONB_FIELDS:
-                set_parts.append(f"{key} = :{param_name}::jsonb")
+                set_parts.append(f"{key} = CAST(:{param_name} AS JSONB)")
                 params[param_name] = json.dumps(value) if value is not None else None
             else:
                 set_parts.append(f"{key} = :{param_name}")