CMP Entity Bean mapping wizard need allow creation
of a set of related CMP entity beans from a
database schema.  At the end, the wizard will push
the mapping info to the plugin for writing out to
server specific descriptors.

The original design for this CMP mapping info push
is that the wizard code going through each bean
and push the mapping one by one using following SPI:

ConfigurationSupport {
    void setMappingInfo(DeploymentConfiguration
config, String ejbName, OriginalCMPMapping mapping);
}

Now that the plugin start using this API, this
design showed weaknesses in that:
- plugin has to write multiple times to file,
causing unecessary file events.
- resolving relationships b/w beans would be more
clumsy.

To eliminate these weaknesses, this API change
proposes the following improvement for single push
protocol:

(1)
ConfigurationSupport {
    void setMappingInfo(DeploymentConfiguration
config, OriginalCMPMapping[] mapping);
} 

(2)
OriginalCMPMapping {
    String getEjbName();
}

(3)
OriginalMappingProvider removed.

Change (1) is not a incompatible change because
the interface is new for this release.  

Change (2) is an incompatible one because it add
access method to existing interface.  However, we
did not expect plugins to use this interface
without the new SPI ConfigurationSupport
introduced in this release. 

Change (3) is for cleanup a interface that is not
going to be used because of change in model of
exchange mapping info b/w CMP wizard and the
plugin code.  The push model is a better choice
with current J2eeserver framework than the pull
model that was used with old J2eeserver framework.
 None of our devmodules are using this SPI, so it
is safe to simply remove it.