Offer the ability to explicitly assemble an application from component bean archives

See the problem described in this comment on CDI-87:
https://issues.jboss.org/browse/CDI-87?focusedCommentId=12626218

Solution proposal 1:

Every beans.xml gets an id:

<beans id="org.jboss.seam.solder">
  ...
</beans>

Then it's possible to depend on other beans.xml files:

<beans id="org.jboss.seam.security">
  <dependency refid="org.jboss.seam.solder"/>
  ...
</beans>

So when guvnor depends on security, it can automatically, transitively inherit solder (without depending on it directly):

<beans id="org.drools.guvnor">
  <dependency refid="org.jboss.seam.security"/>
  ...
</beans>

So when guvnor upgrades to the next version of seam-security, it doesn't need to worry if seam-security still uses seam-solder and whether or not it requires any new bean sets (such as seam-international starting from seam-security 1.2).