2014.10.02 MSS Code Factory 1.10.12418 Add PopDep and DelDep to MSSBam 1.11 model

The 1.11 model needs to enhance the Relation specification with a
RelationDependency which is an optional chain of relationships extending
the PickerPopRelation behaviour by allowing the specification of
a relation chain.  For example, the CFBam 2.0 specification of
a Relation has to include a ToTable and a ToIndex.  The ToTable
can be specified by a PickerPopRelation -- it's simply a selection
of the Table instances owned by a SchemaDef, so it identifies the
relationship of the SchemaDef which identifies the tables owned
by the SchemaDef.  But the ToIndex specification has to depend on
the ToTable specification, so it needs to identify the ToTable
of the Relation first, and then the relation of the TableDef that
identifies an Index of the Table.  i.e. A chain or join of relationships,
which have to be resolved dynamically at runtime and reject their
own resolution if any of the relations in the chain have not been
established.

This construct provides a superset of the PickerPop capabilities,
so those constructs are being removed from the 1.11 BAM.

A second enhancement that is required is similar.  I need to specify
a DeleteDependency of a Table which follows a chain of relationships
similar to the RelationDependancy, but this time with the goal of
identifying sub-objects of a Table n levels down which have to be
deleted before the an instance of the Table object itself can be.
Instead of enhancing the GUI, this will require an enhancement of
the stored procedures used to delete Table instances.  I don't
expect there to be any changes to the object interfaces as a result
of this enhancement -- I think it can be handled entirely through
the stored procedures.  That will enable the deletion of generic
complex objects, which currently can fail on cases like the Relation
of a Table identifying an Index, preventing the deletion of the Index
before the Relations are broken by the delete process in the current
CFDbTest 2.0 "Replace Complex Objects" test.  Once this issue is
addressed, the "Replace Complex Objects" test will pass again.