Unify deployment resolver logic

Currently 3 resolver related interfaces/clsses:

DeploymentScope
EjbModuleEjbResolver
EjbModulePersistenceUnitResolver
MessageDestinationResolver

There is still late resolution in the injector framework as well when it comes to default jndi names. The result of resolution should either be failure or the mapped names of the resolved targets set as the resolvedJndiName on the associated reference metadata such that the injection layer has no resolution logic.

Further, the resolver classes should be collapsed into the DeploymentScope interface. JBossAS has a new DeploymentEndpointResolver interface that can be used to resolve any type of component endpoint:
https://svn.jboss.org/repos/jbossas/projects/integration/trunk/jboss-deployment-spi/src/main/java/org/jboss/deployment/spi/
public interface DeploymentEndpointResolver
{
/**

• Find the deployment endpoint info for the given business interface and
• expected endpoint type.
• @param businessIntf - the interface the endpoint should implement
• @param endpointType - the type of endpoint
• @return the matching endpoint info if found, null otherwise
  */
  EndpointInfo getEndpointInfo(Class businessIntf, String endpointType);

/**

• Find the deployment endpoint for the given reference name. This may be
• relative name qualified by a path prefix, or just the endpoint name.
• @param ref - relative or exact endpoint name
• @param endpointType the type of endpoint
• @return the matching endpoint info if found, null otherwise
• @see EndpointType
  */
  EndpointInfo getEndpointInfo(String ref, String endpointType);

}

The DeploymentScope can either mirror this or be replaced by it and the EjbModuleEjbResolver, EjbModulePersistenceUnitResolver, MessageDestinationResolver dropped in favor of this.