Ensure that RI beans behave correctly even if initializeAfterBeanDiscovery() is not called

If the non-portable mode is enabled, it should be possible to create and inject beans before AfterDeploymentValidation event is fired. This in itself is incorrect CDI SPI usage (see for example CDI-700 and CDI-718). However, we should ensure that RI beans behave "correctly" even if RIBean.initializeAfterBeanDiscovery() is not called yet, i.e. work only with the information available or throw a DefinitionException with a clear explanation.