bannedDependencies.searchTransitive fails with "uses the deprecated Maven Enforcer Plugin API"

### Affected version

3.6.3

### Bug description

Using `searchTransitive` on the `bannedDependencies` rule (https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html) triggers

> ruleName searchTransitive with implementation org.apache.maven.plugins.enforcer.SearchTransitive uses the deprecated Maven Enforcer Plugin API. This will not be supported in a future version of the plugin. Please contact the rule maintainer to upgrade the rule implementation to the current API.

This is regardless of the specific value assigned to `searchTransitive`; the mere presence of the configuration item causes the problem.

If `true`, this will also abort the Maven build process, regardless of any other diagnostics.

This reproduces with Java 17 and Java 21 as the Java runtime.

To reproduce, run `mvn validate` on the attached trivial `pom.xml`

[pom.xml](https://github.com/user-attachments/files/31946527/pom.xml)

Start by running mvn validate with the attached pom.xml using Java 17 or 21, focusing on the bannedDependencies rule and its searchTransitive configuration. Trace where that configuration triggers the deprecated Maven Enforcer Plugin API warning; done means the configuration no longer aborts the build or emits that warning.

Written by the indexing model from the issue text.