Rename vendors to third parties

Renames the user-facing 'vendor' concept to 'third party' across the
entire codebase. The shared common_third_parties reference table is
unchanged.

Migration. Renames the vendor_category enum, the vendors and
vendor_<entity> tables (contacts, services, compliance_reports,
business_associate_agreements, data_privacy_agreements,
risk_assessments) and their vendor_id columns, the asset_vendors /
data_vendors / processing_activity_vendors junction tables,
generated_documents.vendors_document_id, the webhook_event_type
'vendor:<verb>' values, and the snapshots_type 'VENDORS' value.

Backend. Renames coredata models and SQL queries, probo services,
GraphQL / MCP API surface, console / trust / webhook resolvers and
types, the CLI (prb vendor* -> prb third-party*; pkg/cmd/vendormgmt
-> pkg/cmd/thirdpartymgmt), the document generator, vetting agent
prompts, and the common-third-parties-import command.

Frontend, packages, n8n, e2e. Renames apps/console pages, components,
hooks, routes, dialogs, and tabs; the shared @probo/vendors package
(now @probo/third-parties); the @probo/ui Vendors atoms (now
ThirdParties, VendorLogo -> ThirdPartyLogo); the n8n community node
actions/vendor folder (now actions/thirdParty); and the e2e Go test
suite (console and MCP). Filesystem and URL paths use kebab-case
(third-parties), GraphQL fields and TypeScript identifiers use
camelCase (thirdParty / thirdParties), Go types use PascalCase
(ThirdParty), and human-facing text uses 'third party' with a space.

Co-authored-by: Bryan Frimin <bryan@getprobo.com>
Signed-off-by: Bryan Frimin <bryan@getprobo.com>
Signed-off-by: Sacha Al Himdani <sacha@getprobo.com>

pkg/vetting/prompts/market.txt

@@ -1,9 +1,9 @@
 <role>
-You are a market presence analyst. Given a vendor website URL, identify who uses the vendor and triangulate their size to assess market credibility.
+You are a market presence analyst. Given a third party website URL, identify who uses the third party and triangulate their size to assess market credibility.
 </role>
 
 <task>
-Discover customer logos, case studies, "trusted by" claims, partnerships, and company-size signals from the vendor's own website. Report only what you actually find.
+Discover customer logos, case studies, "trusted by" claims, partnerships, and company-size signals from the third party's own website. Report only what you actually find.
 </task>
 
 <assessment>
@@ -11,7 +11,7 @@ Look for and report on:
 
 - **Customer logos** on the home page or a dedicated "Customers" page — list the company names you recognize
 - **Case studies** — links to case studies, success stories, or testimonials; note the featured companies
-- **"Trusted by" sections** — vendors often display "Trusted by X companies" or "Used by" sections
+- **"Trusted by" sections** — third parties often display "Trusted by X companies" or "Used by" sections
 - **Notable partnerships** — technology partnerships, integrations, marketplace listings
 - **Company size indicators** — employee count, funding, revenue, number of customers if mentioned
 
@@ -24,7 +24,7 @@ Most useful entry points: the home page, a `/customers` or `/case-studies` page,
 - **Tier 2**: Well-known mid-market companies, recognized startups, government agencies
 - **Tier 3**: Unknown or unrecognizable company names — still report them but they carry less weight
 
-If the vendor advertises customer counts (e.g. "10,000+ companies"), note the claim and flag whether recognizable names back it up.
+If the third party advertises customer counts (e.g. "10,000+ companies"), note the claim and flag whether recognizable names back it up.
 
 **Company size triangulation** — combine multiple signals:
 - About / Company page: founding year, employee count, office locations