[Feature]: Inconsistent CLI flags between local and routing search commands

[paralta]

Problem Statement

Currently, we have two search commands with inconsistent CLI interfaces:

1. Local DB search (dirctl search): Uses generic --query flags with key=value syntax

   • Example: dirctl search --query "skill-name=images_computer_vision/image_segmentation"

2. Network search (dirctl routing search): Uses specific field flags

   • Example: dirctl routing search --skill "images_computer_vision"

This inconsistency creates a poor user experience where users must remember different flag patterns for similar functionality. The local search's --query approach is verbose and less intuitive compared to the routing search's direct field flags.

Proposed Solution

Standardize the local DB search command to use the same flag pattern as the routing search:

• Replace --query "skill-name=value" with --skill "value"
• Replace --query "name=value" with --name "value"
• Replace --query "locator=value" with --locator "value"
• Replace --query "module=value" with --module "value"
• Replace --query "version=value" with --version "value"

This would make both commands consistent:

• dirctl search --skill "images_computer_vision*" (local)
• dirctl routing search --skill "images_computer_vision" (network)

Alternatives Considered

No response

Additional Context

No response

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing feature request