Modernization, Phase 6 Part 2: Dependency Resolution Verifier configuration cache compatibility

[OdysseusLives]

The Dependency Resolution Verifier is now configuration-cache compatible.

• state lives in a shared DependencyVerificationBuildService
• a DependencyVerificationTask runs after compile/report tasks and records into it
• DependencyResolutionFlowAction runs after the build and reports (and optionally fails) for reporting-only builds.

Verification is split into VerificationEngine, DependencyResolutionErrorFormatter, and VerifierFailureReporter.

The Configurer resolves commit message, tag, includeTransitives, resolution map, and peer coordinates at configuration time

Major changes:

• BuildService + task + FlowAction replace static maps and listeners; verification logic in testable units
• lock/commit inputs fixed at config time.

Breaking changes: None. Extension name string unchanged; internal constant typo fix only.

Notable changes:

• new enableLockFileValidation (default true); reporting-only defers to FlowAction
• verifier registered in afterEvaluate
• global locking and migration tasks are still not config-cache compatible