feat(verification): add Docker-based codegen verification for TypeScript and JSON Schema

[apoorv7g]

This PR introduces a verification pipeline that validates generated TypeScript and JSON Schema output using real toolchains (tsc, ajv). It adds local Mocha verification tests, per-target Docker images with the Concerto CLI, and GitHub Actions workflows to run verification on every pull request.

Changes

• Add local verification test suite under test/verification/ with shared fixtures in cases.js and compile/validate tests for TypeScript (tsc) and JSON Schema (ajv)
• Add verification/corpus/ with a manifest-driven test corpus (Docker corpus is metamodel-only for now; local tests cover the full fixture set under test/codegen/fromcto/data/model/)
• Add Docker verification images:
  • verification/docker/base/ - Node 20, Concerto CLI, branch-linked @accordproject/concerto-codegen
  • verification/docker/typescript/ - generate via CLI + tsc --noEmit
  • verification/docker/jsonschema/ - generate via CLI + ajv compile
• Add scripts/verification/docker-run.js and npm scripts: verify:docker, verify:docker:typescript, verify:docker:jsonschema
• Add .github/workflows/verify-codegen.yml - matrix workflow (typescript, jsonschema) on PR/push to main
• Add .github/workflows/publish-verify-images.yml - publish verification images to GHCR on merge to main / version tags
• Add .dockerignore, verification/templates/tsconfig.json, and verification/docker/targets.json (registry for future targets)

Flags

• Docker corpus currently contains only the metamodel case; additional CTO fixtures will be added to verification/corpus/ in follow-up PRs
• publish-verify-images.yml does not run on PRs - GHCR publishing happens after merge to main; PR verification uses verify-codegen.yml only
• PRs from forks may require a maintainer to approve the GitHub Actions workflow run before checks execute
• When expanding the Docker corpus beyond metamodel, the base image may need a stronger symlink so concerto compile uses this repo's codegen (not the CLI's bundled npm copy)

Screenshots or Video

Local Docker verification (metamodel):

JSONSchema

TypeScript

npm run verify:docker

==> GENERATE metamodel -> Typescript
==> VERIFY metamodel with tsc
==> GENERATE metamodel -> JSONSchema
==> VERIFY metamodel with ajv
schema /work/metamodel/schema.json is valid

Local Mocha verification:

npm run test:verify
14 passing

Author Checklist

• Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
• Vital features and changes captured in unit and/or integration tests
• Commits messages follow AP format
• Extend the documentation, if necessary
• Merging to main from fork:CI-Implementation

[ekarademir]

I think overall very good progress, few comments.

[ekarademir]

Why is this action needed? The other action build and verifies the build no?

[ekarademir]

I'm not sure if we'd ever need t publish these images. What would be the use of it?

[apoorv7g]

Okay, I suggested in my proposal to publish these images, for future reference. If its not necessary , I can omit this, please let me know @ekarademir .