fix(GCI82): fix rule to handle Lombok generated setters

[vimarie]

fix the issue #107

Still some improvements can be done:

• Manage the case when the annotation use is @lombok.Setter or @lombok.Data instead of just @Setter or @Data
• The rule works for the case of import toto.Setter or import toto.Data (same class has Lombok) but some TU and TI can be added.
• Eventually improve the code quality delivered (constant instead of string, test null case).

[MP-Aubay]

Did not have time to test it

[dedece35]

this is the first use case ... using real imports like that.
but there is a second use case missing : if you don't use import but "@lombok.Setter" directly for example
could you add this second use case for all lombok imports ? you can add a second test file and a second unit test to check it.

[dedece35]

I think you can improve more efficiently the import checks. You can add "Kind.IMPORT" in the list of nodes to check. Because Imports are the first statements analyezed in the code, you can know if lombok importrs are present or not.

[github-actions]

This PR has been automatically marked as stale because it has no activity for 30 days.
Please add a comment if you want to keep the issue open. Thank you for your contributions!