Introduce quality rules for Groovy migration (#11636)

feat(ai): Introduce quality rules for Groovy migration

feat(ai): Refine quality rules for Groovy migration

feat(ai): Remove RULE-G03 from Groovy migration quality rules

feat(ai): Add assertion strictness and try-with-resources rules for Groovy migration

Add RULE-C05 to prevent relaxing assertions with matchers and RULE-G05 to prefer try-with-resources over finally blocks with close().

Co-authored-by: bruce.bujon <bruce.bujon@datadoghq.com>

Author: PerfectSlayer

.claude/CLAUDE.md

@@ -3,4 +3,5 @@
 ## Claude Code workflow
 
 - Before creating a pull request, run `/techdebt` to check for technical debt, code duplication, and unnecessary complexity in the branch changes.
+- After running `/migrate-groovy-to-java`, run `/review-groovy-migration` on the migrated files before opening a PR.
 - Always write new unit tests using JUnit 5 and Java. If the target test file is `.groovy`, run the `/migrate-groovy-to-java` skill on it first.