feat: Add JSON output format to configure command

[josecelano]

Overview

Adds JSON output format support to the configure command, implementing roadmap task 12.6 as part of Phase 2 of the JSON output epic (#348).

Changes

New View Module

• Created src/presentation/views/commands/configure/ module with DDD structure
• Implemented ConfigureDetailsData DTO for presentation layer
• Follows the provision/ module pattern with view_data/ and views/ subdirectories

Views Implementation

• JsonView: Renders machine-readable JSON output
  • Returns String with inline error handling (list command pattern)
  • Pretty-printed JSON with all required fields
  • Fallback error JSON on serialization failure
• TextView: Renders human-readable text output
  • Clear field labels and formatting
  • Handles optional instance_ip gracefully

Controller Updates

• Added output_format: OutputFormat parameter to ConfigureCommandController::execute()
• Implemented display_configure_results() method using Strategy Pattern
• Updated router to extract and pass output_format from context

Testing

• ✅ All 8 view tests pass (JsonView, TextView, DTO conversion)
• ✅ All 7 controller tests updated and passing
• ✅ All 2326 library tests pass
• ✅ E2E tested locally with real LXD environment

JSON Output Example

{
  "environment_name": "my-env",
  "instance_name": "torrust-tracker-vm-my-env",
  "provider": "lxd",
  "state": "Configured",
  "instance_ip": "10.140.190.101",
  "created_at": "2026-02-23T08:26:06.789141249Z"
}

Usage

# Default text format (human-readable)
torrust-tracker-deployer configure my-env

# JSON format (machine-readable)
torrust-tracker-deployer configure my-env --output-format json

# Parse with jq
torrust-tracker-deployer configure my-env --output-format json | jq '.instance_ip'

Architecture

• Pattern: Strategy Pattern for rendering (same as provision, list, create commands)
• DDD Layer: Presentation layer only (no business logic)
• Error Handling: Inline fallback for JSON serialization (list pattern)
• Output: Through UserOutput methods (no direct println!)

Related

• Issue: Add JSON output format to configure command #371
• Epic: EPIC: Add JSON output format support #348 - EPIC: Add JSON output format support
• Roadmap: Task 12.6
• Reference: list command (most recent pattern), provision command (module structure)

Closes #371

[josecelano]

ACK 831f177