Fix Msg Schema Error: Honor Mutual Exclusiveness of <Choice>

- Problem: When activating the QueryPersonRequest, the TNVZ returns an
  Identification element that needs to be integrated into the
  msg:DeliveryRequest as a child of Receiver. The Identification child
  is mutually exclusive to another sequence consisting of (Person,
  AustrianAddressesOnly, Address). I forget to delete the sequence
  when adding the Identifcation element and violate the the msg
  schema.
- Solution: Delete sequence when adding Identification.
- Test the fix in test case.

Thanks to Johannes Hörtnagl for pointing out the problem.

0 files changed, 0 insertions, 0 deletions