Add step to forbid module imports

[Plunts]

As per #2679, I added a formatter to forbid module imports.

[Pankraz76]

nice feature thanks.

Might include this documentation fixup as well. Should consider to automate this by an annotation or something @nedtwigg, this is kind of easy to oversee (error-prone).

• #2668

[Plunts]

If you want to fix other things: the test-case for forbidWildcardImports is still called removeWildCardImports 😉 Just say a word and I'll change it together with the documentation, I just wasn't sure how clean you like your PRs 😀

[Pankraz76]

thanks for update and kind offer, for me both fine, it seems tiny.

Let ned or someone else make the call, my opinion obsolete.

[nedtwigg]

the test-case for forbidWildcardImports is still called removeWildCardImports

it would be great to fix that in this PR also, thanks for the offer! An update to the README would be great too.

One smell here is that this is a very small change but our standard protocols make it require a ton of code churn. I'm happy to merge this one, but I don't want to merge a ton of forbidXXX steps that are just verbose wrappers around the forbidRegex step. It's a smell that we need some kind of system for adding a registry of forbidXXX regexes, perhaps even just a central COMMON_REGEX.md where people can share regexes they have found useful in their codebases.

[Pankraz76]

broken due to:

• [openrewrite] Apply GradleBestPractices #2708
• UpdateGradleWrapper: syntax error near unexpected token openrewrite/rewrite#6237

fix in:

• Fix: [openrewrite] disable GradleBestPractices to fix build #2709

[nedtwigg]

@claude merge main, and then run ./gradlew rewriteRun. Try to fix any issues, commit and push.

[nedtwigg]

@claude merge main, and then run ./gradlew rewriteRun. Try to fix any issues, commit and push.