[github] Add CODEOWNERS sync support (#67)

[coisa]

Related Issue

Closes #67

Motivation / Context

• consumer repositories can already sync workflows, git metadata, funding, hooks, and packaged skills, but they still have to author .github/CODEOWNERS by hand
• a static packaged CODEOWNERS file would leak the maintainers of this repository into downstream consumers
• this PR keeps the sync flow useful without hard-coding repository-specific owners into every consumer

Changes

• add a dedicated codeowners command that generates .github/CODEOWNERS from local composer.json metadata
• infer GitHub handles from author homepages, fall back to commented suggestions from support metadata, and prompt for owners in --interactive mode when inference is insufficient
• run codeowners from dev-tools:sync and document CODEOWNERS among synchronized consumer assets
• add focused PHPUnit coverage for the generator, the command, and the sync orchestration path

Verification

• composer dev-tools
• Focused command(s):
  • ./vendor/bin/phpunit tests/CodeOwners/CodeOwnersGeneratorTest.php tests/Console/Command/CodeOwnersCommandTest.php tests/Console/Command/SyncCommandTest.php
  • composer dev-tools changelog:check
  • php bin/dev-tools codeowners --help
  • php bin/dev-tools codeowners --dry-run
  • git diff --check
• Manual verification:
  • confirmed codeowners --dry-run reports the generated .github/CODEOWNERS diff without writing a file
  • confirmed sync documentation and README now describe CODEOWNERS as a generated managed resource

composer dev-tools was also run, but it still fails in this environment during the reports stage because child docs, tests, and metrics subprocesses attempt to open /dev/tty.

Documentation / Generated Output

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

Changelog

• Added a notable CHANGELOG.md entry

Reviewer Notes

• the implementation intentionally does not copy a static CODEOWNERS file with real owners, because that would leak this repository's ownership rules into consumer repositories
• when author metadata is not explicit enough, the generated file stays safe by default and --interactive provides a direct path to populate the catch-all rule

[github-actions]

🚀 Preview is available for this pull request.

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