Do not map safety segment data in connection path to configuration assembly

Currently, the stack assumes either a simple data segment OR a safety network segment is present in an incoming connection path.

This assumption is wrong. Both can be present in the connection path.
With the current implementation, a safety segment will "overwrite" the previsously parsed simple data segment. Instead, of the simple data segment, the safety data segment is mapped to the configuration assembly.

Solution:
When parsing the connection path, the stack shall accept the safety segement but must not store any data coming with the safety segment.