Recent work on CDI made me notice an oddity on how Weld handles PAT for synthetic types (noticed this while writing TCKs for https://github.com/jakartaee/cdi-tck/issues/680).

Technically, all synthetic types should trigger ProcessSyntheticAnnotatedType - a subtype of classical PAT.
For types added via addAnnotatedType(AnnotatedType, String), this works as expected.
However, for those added via configurators it doesn't. In such case we end up firing ordinary PAT instead of synthetic one.

The cause of this seems to be that ContainerEvent#getReceiver() method can no longer detect that a given type was added via an extension. This is because registration of configurator based types actually has to happen after observer method notification.
We should add special handling for those cases.