Galleon source needed by 'dependent' feature packs is not properly organized

We want users of WildFly Core to be able to utilize the Galleon source code it provides without having to have their feature pack depend on org.wildlfy.core:wildfly-core-galleon-pack. This means we want any code that is meant for re-use to not be provided via the core-feature-pack/galleon-feature-pack maven module. The source in that module should only be for things that must be used via dependency on the feature pack it builds.

If any of these items are not wanted for the longer term, create a galleon-pruned module for them.

Also, source elements that might be (really that have been) 'extended' by other feature packs by means of providing a file with the same name should be renamed in core to a name that starts with 'core-'. The 'extensions' can then work by incorporating 'core-xxx'. This last point is primarily about 'basic-profile'.