feat: manage repository config placement

[rozsazoltan]

Summary

Adds repository-managed configuration placement for shared formatter, linter, test, and Rust quality config files.

Projects can now keep Verzly-managed defaults in the workspace root or move them into a dedicated config directory without rewriting package scripts or project-specific command glue.

Changes

• Add [quality.configs] to datarose.toml.
• Support configurable quality config placement:
  • placement = "directory"
  • placement = "root"
• Support custom config directories such as config, tools/config, or .config/verzly.
• Move existing known config files to the configured location during repository update when the destination does not already exist.
• Preserve existing project-local config files by default with update_mode = "preserve".
• Allow intentional baseline replacement through --force or update_mode = "replace".
• Generate tool configs through repository:
  • .clippy.toml
  • rustfmt.toml
  • .oxfmtrc.json
  • .oxlintrc.json
  • vitest.config.ts
  • rector.php
  • phpunit.xml.dist
• Update generated hk.pkl commands to pass explicit config paths to supported tools.
• Update repository check and repository doctor to validate config placement and stale duplicate config files.
• Update the datarose.toml schema and README documentation for the new config placement model.

Notes

This keeps shared Verzly defaults portable across many repositories while still leaving room for project-specific configuration changes. Projects can move config files between the workspace root and a config directory by changing datarose.toml and running verzly repository update.