Add per-invocation lifecycle method and extension support for container templates

[marcphilipp]

Follow-up on #871.

In addition to the existing @BeforeAll, @BeforeEach, @AfterEach, and @AfterAll lifecycle methods, we should add introduce @BeforeContainerTemplateInvocation/@AfterContainerTemplateInvocation (names to be discussed) annotations that can be declared on static (unless TestInstance.Lifecycle.PER_CLASS is used) methods of the test class that will be executed once before/after all test methods and nested classes in a @ContainerTemplate class. If one of those methods is declared in a non-@ContainerTemplate test class, execution of that class or its children should fail to avoid misuse.

For parameterized test classes (see #878), it may make sense to declare composed @BeforeParams/@AfterParams (names to be discussed) annotations that may additionally also support parameter resolution for the argument set of the current container template invocation.

Analoguous to BeforeAllCallback etc., new BeforeContainerTemplateInvocationCallback/AfterContainerTemplateInvocationCallback (names to be discussed) extension interfaces should be introduced as well to externalizing behavior to extensions.

Deliverables

• Introduce @BeforeContainerTemplateInvocation/@AfterContainerTemplateInvocation lifecycle method support
• Introduce BeforeContainerTemplateInvocationCallback/AfterContainerTemplateInvocationCallback extension points