Resolve and install transitive registryDependencies for registry items

[rakibulism]

Motivation

• Components/blocks can declare registryDependencies and the CLI needs to fetch and install those transitive dependencies before installing the requested item.
• The add flow must remap targets and install dependencies in topological order so projects get all required files without manual steps.
• The resolver should surface clear errors for missing dependencies and dependency cycles.

Description

• Added resolveItemWithDependencies to the registry resolver to fetch an item and all transitive registryDependencies in topological order and detect cycles, and kept resolveItem as a thin wrapper around it.
• Updated runAdd to call resolveItemWithDependencies, remap targets for every resolved item, install each dependency item before the requested item, and return an installed list in the result along with accumulated written files.
• Exported resolveItemWithDependencies from the registry index and updated imports in the add command to use it instead of resolveItem.
• Enhanced tests and fixtures: expanded add.test.ts to expect dependency installation and updated registry/resolver.test.ts to test dependency ordering, missing transitive dependency errors, and cycle detection; adjusted mocked fetch and fixture items to simulate registryDependencies.

Testing

• Ran resolver unit tests in packages/cli/src/registry/resolver.test.ts which exercise listRegistryItems, resolveItem, and the new resolveItemWithDependencies cases for ordering, missing dependency, and cycles, and they passed.
• Ran integration/unit tests in packages/cli/src/commands/add.test.ts which verify remapped targets, dependency installs, and snippet behavior, and they passed.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f18c14cc7a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".