Change implicit relation of satellite mappings to more likely behaviour

[mattywausb]

Currently satellite content (or any content) will be mapped to all parent relations(key sets), when the mapping is the only one for the column and no relation(key set) is declared.

It is less likely for content to belong to multiple key sets, therefore declaration of belonging to multiple key sets must be explicit(*). Without declaration, a content mapping belongs to the unnamed key set or the key set of the parent, when there is only one.

This differs from key mappings, where no declaration of key set means a belonging to all key sets. (Implicit *)

0.6.1

• [x] essential multi case test 0056 created/adapted
• [x] documentation adapted
• [x] Existing test cases specification adapted (add * on default mappings)
• [x] Existing test cases adapted (add * on default mappings)
• [x] dvpdc adapted
• [x] test reference data adapted

0.6.2

• [x] check test specification extended (nothing to do)
• [x] test specifications for more scenarios
• [ ] test 3070 implemented
• [ ] test 3340 implemented
• [ ] test 3690 implemented

[mattywausb]

For satellites

• any explicit key set must be complete (* is possible)
• without any declaration
  • matches to parents with single key set
  • matches to unnamed of parent

For hubs/link content the same rules apply but the key set is that of the own table.

Scenarios:

• parent unnamed single
• parent unnamed+named
• parent single named
• parent multiple named Vs
• sat all undeclared
• sat all single named
• sat some undeclared(unnamed) some named
• sat all multiply named
• mix with * mappings

Check scenarios:

• incomplete mappings
• unknown relations