Early solution for SGF-248 concerning bootstrapping a Spring ApplicationContext inside a GemFire Server-based JVM process when starting the GemFire Server from Gfsh.
Fixed TOOD-based Javadoc comment misspelling.
Renaming the SpringContextBootsrappingInitializerTest to SpringContextBootstrappingInitializerIntegrationTest to reflect the fact that the test class is actuall an 'integration' test.  Also renamed the cache-with-initializer.xml GemFire native configuration file to cache-with-spring-context-bootstrap-initializer.xml to indicate that we are using GemFire to bootstrap a Spring container.
Completed all testing and interface/functional changes for SGF-248 - Bootstrapping a Spring ApplicationContext with GemFire.
Added support to the SpringContextBootstrappingInitializer class for component scanning given a set of base packages to scan.  Refactored LazyWiringDeclarableSupport to implement the DisposableBean interface in order for any extending bean component to unregister itself from the SpringContextBootstrappingInitializer to stop receiving  ApplicationContext event notifications when destroyed.  Fully tested the application component scanning and configuration using Annotations and JavaConfig-based configuration, uplifting some of the application components (UserDao, UserService, etc) from the integration test and adding a UserApplicationConfiguration @Configuration component in order to test this functionlity properly.
Added Javadoc reference to the Spring DisposableBean interface in the class header.