feat: add ze-types cli

[Nsttt]

What's added in this PR?

• New ze-types package + CLI to generate MF types.
• Default path: reads zephyr:dependencies from nearest package.json and resolves via Zephyr API.
• Optional path: pull remotes from Zephyr zephyr-manifest.json URLs.
• Generates ze-types.d.ts module mapping for types: ["ze-types"] in tsconfig.
• ESLint override scoped to libs/ze-types to allow Error throws.

Screenshots

• N/A

What's the issues or discussion related to this PR ?

Need a simple DX flow to consume MF types from Zephyr remotes without manual URL wiring; prefer zephyr:dependencies in package.json as default.

What are the steps to test this PR?

• pnpm nx run ze-types:lint
• pnpm nx run ze-types:build
• In a repo with zephyr:dependencies (e.g. zephyr-cloud-io):
  • ZE_SECRET_TOKEN=... npx ze-types
  • Add types: ["ze-types"] to tsconfig, verify imports resolve.

Documentation update for this PR (if applicable)?

• Not yet.

(Optional) What's left to be done for this PR?

• Run lint/build locally.
• Add docs entry if we want external usage guidance.

(Optional) What's the potential risk and how to mitigate it?

• Requires auth token to resolve zephyr:dependencies; failures if token missing. Mitigate by setting ZE_SECRET_TOKEN or using --url with manifest.

(Required) Pre-PR/Merge checklist

• I have added/updated/opened a PR to documentation to cover this new behavior
• I have added an explanation of my changes
• I have written new tests (if applicable)
• I have tested this locally (standing from a first time user point of view, never touch this app before)
• I have/will run tests, or ask for help to add test

[Nsttt]

Closing for now, can be picked up later if needed.