[output] Roll out structured output across commands and workflows (#33)

[coisa]

Related Issue

Closes #33

Motivation / Context

• provide a repository-wide structured-output strategy for DevTools instead of a changelog-only rollout
• keep the interactive human-readable CLI experience intact while giving CI, bots, and AI-agent workflows deterministic machine-readable output
• make nested command orchestration and GitHub Actions logs easier to inspect without pushing output-formatting concerns down into every command

Changes

• standardize --json and --pretty-json across the DevTools command surface, including pretty-printed terminal JSON and agent-aware JSON defaults when the runtime is detected as agent-driven
• centralize command-context extraction through logger processors so commands pass input / output and the logger expands command, arguments, options, and buffered command output consistently
• move GitHub Actions error annotations into the logger so logged failures automatically emit workflow annotations, including file / line metadata when commands provide it
• introduce GithubActionOutput and use it from ProcessQueue to group queued subprocess output into collapsible workflow sections with cleaner labels in CI
• migrate orchestration-heavy commands such as standards and reports to the shared queue flow so nested command execution, buffering, and workflow presentation are handled consistently
• propagate structured-output flags through nested DevTools subprocesses and prefer quieter subprocess modes when machine-readable output is active
• replace the negative --no-progress flag with positive --progress, keeping supported commands quiet by default while still allowing explicit progress in text-mode runs
• normalize result logging through shared command traits and improve GitHub Actions visibility without changing command exit semantics
• expand PHPUnit coverage for logger behavior, queue behavior, command orchestration, and CI-specific GitHub Actions output expectations
• refresh README, command guides, running guides, troubleshooting notes, and changelog coverage for the final behavior shipped by this branch

Verification

• COMPOSER_NO_INTERACTION=1 composer dev-tools:fix
• Focused command(s):
  • composer dev-tools tests -- --filter='(ProcessQueueTest|ReportsCommandTest|StandardsCommandTest|TestsCommandTest|RefactorCommandTest|CodeStyleCommandTest|PhpDocCommandTest|DocsCommandTest|MetricsCommandTest)'
  • composer dev-tools tests -- --filter='(GithubActionOutputTest|ProcessQueueTest|OutputFormatLoggerTest|ReportsCommandTest|StandardsCommandTest)'
• Manual verification:
  • confirmed GitHub Actions workflow commands are emitted only when supported
  • confirmed queued subprocess labels are human-readable in workflow groups
  • confirmed structured output remains deterministic while nested tools stay quiet unless --progress is requested in text mode

Documentation / Generated Output

• README updated
• docs/ updated
• Generated or synchronized output reviewed

Changelog

• Added a notable CHANGELOG.md entry

Reviewer Notes

• this PR now covers the full structured-output foundation for DevTools commands, including logger integration, nested subprocess propagation, workflow annotations/groups, and the progress-control contract
• the branch also stabilizes CI expectations so GitHub Actions-specific output stays deterministic in the PHPUnit suite

[github-actions]

🚀 Preview is available for this pull request.

• Docs: https://php-fast-forward.github.io/dev-tools/previews/pr-146/
• Coverage: https://php-fast-forward.github.io/dev-tools/previews/pr-146/coverage/
• Metrics: https://php-fast-forward.github.io/dev-tools/previews/pr-146/metrics/