[perf] cache Method and Field instances when PostConstruct processing is done and default LifecycleProvider is set

Each time a managed bean is created, it is inspected for PostConstruct/PreDestroy annotations. The default algorithm does not cache that information. Usually the container do that, so this effect is not seen in containers like Tomcat and others (MyFaces provide a LifecycleProvider for them).

By default, we can use the same trick for MetaRulesetImpl, that has a WeakHashMap<ClassLoader, Map<..., ...> > so when the application is undeployed, no cyclic reference is hold.