Forward port Maven 3.10.0 PluginDependenciesResolver changes

[cstamas]

Also, restore binary compatibility that was broken in 4-beta-2.

This PR aligns PluginDependenciesResolver with changes happened in Maven 3.10.x, and also restores binary incompatibility happened in DefaultPluginDependenciesResolver that used to be injected directly.

[cstamas]

@gnodet master is broken with this same error

[gnodet]

Nice work aligning the Maven 4.x PluginDependenciesResolver with the 3.10.x changes and restoring the binary compatibility broken in 4-beta-2. The deprecation+delegation pattern is correctly applied, and switching to interface-based injection in BootstrapCoreExtensionManager is the right move.

A couple more observations not tied to specific lines:

• TODO comment: Both BootstrapCoreExtensionManager files (compat and impl) have a TODO comment above the call site that still references resolveCoreExtension. Since the method is now resolveCoreExtensionAndFlatten and the method is now on the interface, the TODO may be partially addressed and could be refined.
• @since 3.10.0 on new interface methods: The new methods use @since 3.10.0, which correctly references where they originated, but since Maven 4.x and 3.10.x are separate release lines, consumers reading the Maven 4.x javadoc might find this confusing. Flagging for awareness only.
• No tests added: No new or modified tests, which is reasonable for an interface evolution / binary compat PR where the behavior is unchanged (new methods delegate to the same resolveInternal logic).

This review does not replace specialized AI review tools (CodeRabbit, Sourcery) or static analysis (SonarCloud).

Fully automatic review from Claude Code