[java] Update AvoidSynchronizedAtMethodLevel message to mention ReentrantLock, new rule AvoidSynchronizedStatement

[chonton]

see https://openjdk.org/jeps/8337395

Describe the PR

Modify advice for AvoidSynchronizedAtMethodLevel and add AvoidSynchronizedStatement.
See https://openjdk.org/jeps/8337395 for detailed information about virtual thread pinning concerns.

Related issues

• Fixes #

Ready?

• Added unit tests for fixed bug/feature
• Passing all unit tests
• Complete build ./mvnw clean verify passes (checked automatically by github actions)
• Added (in-code) documentation (if needed)

[ghost]

	1 Message
📖	Compared to master: This changeset changes 969 violations, introduces 1689 new violations, 0 new errors and 0 new configuration errors, removes 0 violations, 2 errors and 7 configuration errors. Download full report as build artifact
✅	Compared to master: This changeset changes 969 violations, introduces 1689 new violations, 0 new errors and 0 new configuration errors, removes 0 violations, 2 errors and 7 configuration errors. Download full report as build artifact
✅	Compared to master: This changeset changes 969 violations, introduces 1689 new violations, 0 new errors and 0 new configuration errors, removes 0 violations, 2 errors and 7 configuration errors. Download full report as build artifact

Generated by 🚫 Danger

[jsotuyod]

@chonton thanks for the PR!

This looks overall very good, but the new rule AvoidSynchronizedStatement would require tests. Doing so in PMD is quite easy, simply create an empty AvoidSynchronizedStatementTest similar to the one for AvoidSynchronizedAtMethodLevelTest. And then create a copy of AvoidSynchronizedAtMethodLevel.xml for AvoidSynchronizedStatement, replacing the test samples appropriately.

If the names between rule, test and xml match as expected, they will be run automatically.

[adangel]

Thanks!