cua-driver skill should print the installed skill path

[f-trycua]

Problem

Running cua-driver skill currently falls through to the implicit MCP tool-call route and fails with:

Permission denied: tool 'skill' has no reviewed risk classification

This is surprising when an agent or user casually asks the CLI where its bundled skill lives.

Scope

Treat the exact singular command cua-driver skill as a read-only shortcut for the existing cua-driver skills path behavior. Keep the plural skills {install|update|uninstall|status|path} management surface unchanged.

Acceptance evidence

• cua-driver skill exits successfully without a daemon and prints exactly the local skill-pack directory.
• cua-driver skills path continues to print the same directory.
• finite-command/operation classification reports the alias as the reviewed read-only skills/path operation.
• focused Rust tests pass across the shared CLI implementation.

Selected for implementation by the maintainer request that reported the reproducer.