Fix post-upstream-merge metadata regressions

[tomjtobinn]

Summary

• restore upstream standard metadata synchronization and workspace-migration behavior for object, field, index, view, and view-field creation
• preserve immutable upgrade history and remove stale standard Calendar Event record-page metadata through the 2.25 workspace upgrade
• retain the Calendar Event record-page metadata required by the public call-recorder and twenty-fireflies applications without changing the core Twenty UI layout
• align workspace-manager callers with the upstream synchronization API
• add notIn list filtering for supported scalar types across GraphQL and REST, including the generated client schemas and types
• add regression coverage for standard metadata synchronization, field/index creation, cross-version workspace upgrades, Calendar Event reconciliation, and list-filter operators

Validation

• GitHub CI is fully green at 12f928e17e
  • server lint, typecheck, build, and validation passed
  • all 4 server unit-test shards passed
  • all 16 server integration-test shards passed
  • cross-version upgrade and previous-version mutation guard passed
  • all public application installation smoke tests passed
  • front, UI, and shared aggregate checks passed
• focused Node 24 unit validation passed: 2 suites, 245 tests, and 85 snapshots
• application unit suites passed: 567 tests
• focused metadata snapshots passed
• clean-database Node 24 integration rerun passed using isolated Redis
• Node 24 backend booted successfully
• current Go develop compatibility validation against this PR passed: 28 passed, 5 expected skips, 0 failures; focused compatibility tests passed 3/3
• lint, formatting, generated-diff, and targeted type checks passed

Remaining local-test caveat

Full Twenty Playwright UI E2E was not run locally because the completed frontend/E2E dependency environment was unavailable. The GitHub checks listed above are green; the Go-on-Twenty compatibility suite was run locally and passed.