[prone] remove failing tech.picnic.error-prone-support

[Pankraz76]

tryout reduce warnings for:

• Removing error-prone from our build #2745
• Allow foreign executables to explicitly specify "use any found version" with '*' #2758
• new step to expand java wildcard imports #2744
• [prone] fix warning StaticImport, NonStaticImport #2743
• consider convention principle for disableAllWarnings=true google/error-prone#5367

Please DO NOT FORCE PUSH. Don't worry about messy history, it's easier to do code review if we can tell what happened after the review, and force pushing breaks that.

Please make sure that your PR allows edits from maintainers. Sometimes it's faster for us to just fix something than it is to describe how to fix it.

After creating the PR, please add a commit that adds a bullet-point under the [Unreleased] section of CHANGES.md, plugin-gradle/CHANGES.md, and plugin-maven/CHANGES.md which includes:

• a summary of the change
• either
  • a link to the issue you are resolving (for small changes)
  • a link to the PR you just created (for big changes likely to have discussion)

If your change only affects a build plugin, and not the lib, then you only need to update the plugin-foo/CHANGES.md for that plugin.

If your change affects lib in an end-user-visible way (fixing a bug, updating a version) then you need to update CHANGES.md for both the lib and all build plugins. Users of a build plugin shouldn't have to refer to lib to see changes that affect them.

This makes it easier for the maintainers to quickly release your changes :)

[Pankraz76]

also rewrite, not spotless, ending up being error prone as well completing the circulation.

• spotless/rewrite.yml

  Line 34 in 78cc9ed

  - org.openrewrite.staticanalysis.MissingOverrideAnnotation

[Pankraz76]

have you updated the github version somehow @nedtwigg ?

Now its keeping the diff even after forbidden force push.

Now its seems ready consider suppressing all the warnings.

[Pankraz76]

zero warnings as requsted: