Clarify when BeanManager.createBeanAttributes(AnnotatedMember) returns an alternative

Currently, a producer field/method is an alternative if it is annotated with @Alternative or an alternative stereotype or the class declaring the field/method is annotated this way. However, when the BeanManager.createBeanAttributes(AnnotatedMember) method is called, the container has no access to the bean that declares the member. Therefore, the specification should clarify whether the container

• should examine the AnnotatedType for @Alternative or alternative stereotypes
• should try to infer the declaring bean (probably not possible since multiple beans may exist, each of them possibly modified in the ProcessBeanAttributes phase, etc.)
• should make an assumption (e.g. the bean that declares the returned BeanAttributes is always assumed not to be an alternative)