feat: refresh the Context.dev n8n integration

[aadithyanr]

Summary

• rebrands the node and credential UI to Context.dev while retaining the published package name and internal IDs so existing installations keep upgrading
• adds a version 2 node with all 45 operations in the current public OpenAPI contract, including News, web search/scraping, extraction, parsing, people, monitors, batches, webhooks, and utility APIs
• keeps saved version 1 workflows on their original operation shapes and routes, now served through https://api.context.dev/v1
• adds binary parsing, path encoding, idempotency support, destructive-operation confirmation, item pairing, and continue-on-fail handling
• refreshes the Context.dev branding, documentation, CI, package metadata, license, and release provenance workflow

/web/answers is intentionally not included because it is not part of the current production OpenAPI surface.

Validation

• npm ci on Node.js 24
• npm run check
  • strict n8n lint passed
  • 11 unit/execution tests passed
  • live OpenAPI contract test passed with exact 45-route parity
  • build passed
  • production dependency audit: 0 vulnerabilities
• npm pack --dry-run: 41 expected files, 138,370 bytes unpacked, no source/tests/build metadata leaked
• production smoke tests returned HTTP 200 for credentials/limits, NAICS, News, Markdown scraping, binary parsing, current brand retrieval, and the retained legacy brand route
• all user-facing Context.dev and n8n documentation links returned HTTP 200

[contextualbeer]

Wouldn't this be better to link to the API reference of the specific operation here? Or am I misunderstanding the code?