Skip JUnit 4 lifecycle annotation when Jupiter equivalent already present

[timtebeek]

What's changed

UpdateBeforeAfterAnnotations migrated JUnit 4 lifecycle annotations by changing their type to the Jupiter equivalent. When a method already carried both the JUnit 4 annotation and its Jupiter equivalent — e.g. a shared base class supporting both frameworks:

class TestBase {
    @Before
    @BeforeEach
    void setup() {
    }
}

changing @Before to @BeforeEach produced a duplicate, non-repeatable annotation, yielding the compile error:

Duplicate annotation. The declaration of 'org.junit.jupiter.api.BeforeEach' does not have a valid java.lang.annotation.Repeatable annotation

Now, before the type-change passes run, any JUnit 4 lifecycle annotation whose Jupiter equivalent is already present on the same method is removed instead.

• Fixes UpdateBeforeAfterAnnotations does not check for existing target annotations #501