[FEATURE] Show deployment targets and MCP counts in deps list

Is your feature request related to a problem? Please describe.

When packages are installed for multiple agents, apm deps list --all does not show which targets each package was deployed to. Its primitive columns include Skills and Hooks, but no MCP server count, so MCP-only packages are difficult to understand from the table.

This was observed with APM 0.30.0. Users currently need to inspect manifests, lockfiles, or agent configuration files to answer these questions. apm mcp list lists registry servers rather than installed connections.

Describe the solution you'd like

Add two columns to apm deps list:

• Targets: each package's recorded deployment targets, such as kiro, codex. Use per-package deployment records rather than assigning every configured project target to every package. If records are unavailable, show an explicit unknown value.
• MCPs: the number of MCP servers bundled with the package, alongside the existing primitive counts. Include MCP-only packages even when they contain no skills.

As a related enhancement, support --target kiro to filter packages by their recorded target. Both columns and filtering should work for project installs, --global, and --all, preserving the scope distinction.

For example, a package deployed to Kiro and Codex with two MCP servers and no skills should show both targets, MCPs = 2, and Skills = 0. It should appear with --target kiro and be excluded when filtering for an agent it was not deployed to.

The target column describes recorded deployments, and the MCP count describes package contents; neither should imply that an MCP connection is currently healthy or authenticated. The two columns would be the priority, with filtering as a useful follow-up if needed.

Describe alternatives you've considered

Inspecting apm.yml, apm.lock.yaml, and each agent's MCP configuration works but makes a basic installed-package inventory cumbersome. Target filtering alone helps narrow results but does not make deployment targets discoverable in the default list.

Additional context

Related: #2070 concerns machine-readable CLI output, and #2948 concerns interactive removal of installed plugins. This request focuses on visibility in the dependency list.

Start with the implementation of apm deps list --all, then inspect how deployment records are stored alongside apm.yml, apm.lock.yaml, and agent configuration. Compare its package inventory with apm mcp list before adding the Targets and MCPs data, preserving project, --global, and --all scope distinctions. Done means the example package displays both targets and its MCP count, including when it has no skills.