[Save All] Move getAllModifiedObjects to capability

Moves getAllModifiedObjects to a capability.
This simplifies AbstractComponent API (this
method is rarely overridden; only one plug-in
uses this behavior) and gives some flexibility
to handling of modified objects to those
plug-ins. Supports nasa/MCT-Plugins#72
[Save All] Move Save All notification to capability

As with getAllModifiedObjects, move
notification of a successful Save All
to a capability in order to further
simplify AbstractComponent with regard
to the rarely-used Save All functionality.
[Save All] Notify work unit delegate on save

A work unit delegate may also be responsible
for managing the aggregation of dirty objects
in support of Save All, so notify it when a
component has been saved.
[Save All] Merge latest from master
[Save All] Back explicit object manager map

Use a map of id to component to track modified
objects in the explicit object manager. This
means that if multiple versions of the same
component are explicitly added as modified
objects, only the latest is actually returned
in a subsequent getModifiedObjects. This
avoids Save All ambiguities in cases where
multiple versions of the same object are
returned in getModifiedObjects.
Merge branch 'master' into mctPlugins72
[Save All] Test ObjectManager implementations
[Save All] Amend test to increase coverage
Merge pull request #206 from VWoeltjen/mctPlugins72

[Save All] Move getAllModifiedObjects to capability
[Taxonomy] Add API for plugin-introduced bootstraps

Issue nasa/mct#207 describes the need
for allowing third-party plug-ins to
introduce their own bootstrap components.
This adds appropriate method signatures
to plug-in API to facilitate this. This
does not include any implementation for
the usage of this API.
[Taxonomy] Use plugin bootstrap API

When bundles are refreshed, aggregate all
bootstrap components exposed by plugins,
filter out any which have been previously
written to the database, and persist.
[Taxonomy] Add Bootstrap capability definition

Adds a Bootstrap capability which
bootstrap components may support in
order to provide additional information,
such as ordering, related to such
components.
[Taxonomy] Use Bootstrap capability

Use the Bootstrap capability to determine
if a component should appear as a global
or creator-specific bootstrap component,
when tagging bootstrap components exposed
by plugins.
[Taxonomy] Use capability to find My Sandbox
[Taxonomy] Sort bootstrap components
[Taxonomy] Updated version requirements

Updated package versions required in
bundles to reflect increment in
package version due to introduction
of Bootstrap capability.
[Taxonomy] Support Bootstrap capability in Sandbox

Add Bootstrap capability to My Sandbox.
This identifies the sandbox as the
default destination for new components
to the platform, and provides indexing
information to ensure that My Sandbox
always appears at the last position
in the User Environment.
[Taxonomy] Support Bootstrap capability in taxonomy comp

Add Bootstrap capability to
TelemetryDataTaxonomyComponent. These
are not always bootstraps, but when they
are bootstraps, they should be located
shortly before My Sandbox.
[Taxonomy] Change comment to satisfy checkstyle
[Taxonomy] Test bootstrap components