Add support for class-level Lombok @Getter and @Setter annotations

[Ouweshs28]

What's changed?

• Added UseLombokGetterOnType and UseLombokSetterOnType recipes to hoist default field-level Lombok accessor annotations to the class level.
• Added the recipes to LombokBestPractices after the existing field-level accessor conversions.
• Updated recipes.csv.
• Added positive, negative, and composite-recipe coverage.

What's your motivation?

• Closes Hoist Lombok @Getter/@Setter to class level if appropriate #1047.

Anything in particular you'd like reviewers to focus on?

Please review the eligibility rules for static, final, $-prefixed, configured, and mixed variable declarations. These fields retain their field-level annotations when Lombok type-level accessors would not generate equivalent methods.

Anyone you would like to review specifically?

N/A

Have you considered any alternatives or workarounds?

I considered extending the existing field-level getter/setter recipes directly and using the external summarization recipes referenced in the issue. Separate composable recipes keep existing behavior stable while allowing LombokBestPractices to hoist annotations after field-level conversion.

Any additional context

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've run ./gradlew build locally, and committed any resulting changes to recipes.csv
• I've formatted the lines I changed, without reformatting code I didn't touch