Fix GrumPHP config paths for global dev-tools sync

[coisa]

Related Issue

Closes #288

Motivation / Context

• global dev-tools sync was persisting DevTools-owned GrumPHP config paths in consumer composer.json, which breaks when the path is machine-specific
• Git hooks were the only consumer of that managed path, so the path should stay local to the installed hooks rather than committed metadata

Changes

• remove deprecated DevTools-managed extra.grumphp.config-default-path values while preserving consumer-owned GrumPHP settings
• render packaged Git hooks with the active DevTools grumphp.yml path at install time, while still preferring a project-local grumphp.yml
• add dedicated synchronizer and hook renderer coverage, plus docs/changelog updates for the legacy transition

Verification

• composer dev-tools
• Focused command(s): composer dev-tools tests -- --filter=(ManagedConfigPathSynchronizerTest|UpdateComposerJsonCommandTest|GitHooksCommandTest|HookContentRendererTest|PackagedHooksTest|SyncCommandTest)
• Manual verification:

Documentation / Generated Output

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

Changelog

• Added a notable CHANGELOG.md entry

Reviewer Notes

• .github/wiki remained dirty locally before this work and was not included in the commit.

[github-actions]

🚀 Preview is available for this pull request.

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a2ef340b0d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Normalize composer.json base directory before sync

updatedComposerJsonContents() passes dirname($file) directly into ManagedConfigPathSynchronizer::synchronize(). With the default --file value (composer.json), this becomes . (a relative path), and isManagedConfigPath() then calls Path::makeRelative() with an absolute managed path and a relative base path, which raises InvalidArgumentException. In practice this causes default update-composer-json/dev-tools:sync runs to fail instead of updating metadata.

Useful? React with 👍 / 👎.