Replace ajv with zod; simplified plugin API

[keller-mark]

Fixes #1430
Fixes #1289
Towards #1401
Closes #1100
Towards #1515
Fixes #1514

Changes in this PR:

• Multiple passes of config validation/parsing
  • 1. in <Vitessce/> to support upgrading from previous config schema versions - but plugin-agnostic
  • 2. in <VitS/> against the latest config schema - but plugin-agnostic
  • 3. in <VitS/> against a plugin-specific schema which accounts for coordination type value schemas and file type options schemas
• Validation of plugin coordination type value schemas and file type options schemas via Zod
  • These validations now happen by building a plugin-specific config schema
  • Coordination type plugins accept a Zod schema for their value.
  • File type plugins accept a Zod schema for their options.
  • @vitessce/schemas and vitessce re-export z from Zod
  • superRefine calls for schema upgrades to catch deprecated coordination types.
  • Perform validation for cellSets/obsSets JSON/CSV imports using Zod rather than Ajv
• Plugins no longer registered via window (if this is needed it should be done in user-land) - instead they are passed as props to <Vitessce/> / <VitS/>
• Introduction of TypeScript in @vitessce/plugins and @vitessce/schemas
  • I had hesitated to do this for a while but I think Vitessce is stable enough now that it will help to start using TypeScript where possible
• Linting for JSX, TS, and TSX

Updated docs

• React component
• Plugin development
• Config schema versioning

Future PRs:

• plugin data types to replace DATA_TYPE_COORDINATION_VALUE_USAGE
• plugin coordination types define autoIndependent
• "decentralize" COMPONENT_COORDINATION_TYPES
• auto-generate JSON schemas using zod-to-json-schema and publish to NPM to enable validation in external tools (e.g., vitessce-Python/R)

Checklist

• Ensure PR works with all demos on the dev.vitessce.io homepage
• Open (draft) PR's into vitessce-python and vitessce-r if this is a release PR
• Documentation added or updated

[ilan-gold]

Can this be inferred from the schema itself? zod probably has a notion of default values, no?

[keller-mark]

Good point - it does https://zod.dev/?id=default although I think for now I will just make an issue to investigate/address in a follow-up PR