Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle

I believe we should not break the application initialization lifecycle.

So it might be reasonable to state that SeContainerInitializer.addAnnotatedTypes() maps to AfterTypeDiscovery.addAnnotatedType(AnnotatedType<?>, String) (note that we would have to sort out missing id) and SeContainerInitializer.addBeans() maps to AfterBeanDiscovery.addBean(Bean<?>).

The other solution would be to remove these methods and introduce the concept of "synthetic container lifecycle event observers" and leverage the configurators API. See also http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/.