Drop RedundantModifier to SUGGESTION and FinalClass to WARNING

[carterkozak]

Before this PR

After this PR

==COMMIT_MSG==
Drop RedundantModifier to SUGGESTION and FinalClass to WARNING

These checks don't imply bugs, and automation will fix failing cases automatically, so it's not necessary to block compilation.
FinalClass moved to warning rather than suggestion because there are a few edge cases (e.g. dependent projects using mockito without inline mock maker) where releases can run into issues if the bots don't fix findings in time.
==COMMIT_MSG==

Possible downsides?

Code on develop may have issues detected, but not fixed.

Based on comments from @iamdanfox.

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Drop RedundantModifier to SUGGESTION and FinalClass to WARNING

These checks don't imply bugs, and automation will fix failing cases automatically, so it's not necessary to block compilation.
FinalClass moved to warning rather than suggestion because there are a few edge cases (e.g. dependent projects using mockito without inline mock maker) where releases can run into issues if the bots don't fix findings in time.

Check the box to generate changelog(s)

• Generate changelog entry

[carterkozak]

bulldozer?