Task: Add XTS CLI integration for centrally-managed device allocation commands

[Ulrond]

Description

Integrate support for centrally-managed command definitions served from allocator servers. The XTS tool should load and execute commands from .xts files without namespace conflicts with built-in plugins.

Goals:

• Enable users to register allocator commands via: xts alias add allocator http://server:5000/xts_allocator.xts
• Support hierarchical command namespaces (e.g., xts allocator slots allocate)
• Resolve conflicts between .xts file commands and built-in plugins
• Allow command evolution without XTS client tool updates

Current Issues:

• Namespace collision: .xts files with allocate commands conflict with built-in allocator plugin
• Need proper command hierarchy support for aliased .xts files
• Commands should be accessible under alias prefix (e.g., xts allocator ...)

Approach:

• Fix yaml_runner command parsing to support nested namespaces under alias prefix
• Prevent .xts file commands from colliding with built-in plugin commands
• Ensure aliased commands are properly scoped and accessible

Benefits:

• Central command management from servers
• No XTS tool updates needed for new server features
• Consistent CLI across different allocator/test servers

Notes

• Related to xts_allocator_server integration
• .xts file format already defined and working (served at /xts_allocator.xts)
• Test server running at localhost:5000 for development/testing

[Ulrond]

Multi-Server Federation Requirement

Use Case: Support multiple allocator servers with both targeted and federated queries.

Workflow:

# Register multiple servers
xts alias add allocator-lab-a http://lab-a:5000/xts_allocator.xts
xts alias add allocator-lab-b http://lab-b:5000/xts_allocator.xts
xts alias add allocator-dev http://localhost:5000/xts_allocator.xts

# Query specific server
xts allocator-lab-a slots list

# Query ALL allocator servers (federated view)
xts allocator slots list  # Aggregates results from all allocator-* aliases

Implementation Requirements:

• Track alias types/categories (e.g., all allocator-* are allocator servers)
• When base command used without server suffix, query all matching servers
• Parallel requests to all servers for performance
• Tag results with server origin (e.g., [lab-a], [lab-b])
• Consolidate and display unified output
• Handle partial failures gracefully (show available results)

Benefits:

• Single command to see all available resources across labs
• Still supports targeted queries to specific servers
• Natural namespace: allocator = all, allocator-lab-a = specific