DDSSEC11 — GUIDs for new builtin Topics do not comply with DDS-RTPS specification

According to DDS-RTPS specification version 2.2 section 9.3.1.2 (Mapping of the EntityId_t) the last octet of the EntityId_t part of GUID for a builtin DataWriter and DataReader takes a specific value that depends on whether the builtin entity is used to send Topic whose data-type is keyed or unkeyed.

RTPS uses the name EntityKind to refer to this last octet in the EntityId_t.
According to Table 9.1 of the DDS-RTPS specification:

• A builtin DataWriter of a keyed TopicType shall have EntityKind 0xc2.
• A builtin DataReader of a keyed TopicType shall have EntityKind 0xc7.

• A builtin DataWriter of a non-keyed TopicType shall have EntityKind 0xc3.
• A builtin DataReader of a non-keyed TopicType shall have EntityKind 0xc4.

This is inconsistent with some of the values defines in Table 9 ( section 7.3.7.1) of the DDS-Security 1.0 spec. In particular the following ones:

• BuiltinParticipantStatelessMessageWriter has EntityKind 0xc2 but it should be 0xc3 because its TopicType has no key.

• BuiltinParticipantStatelessMessageReader has EntityKind 0xc7 but it should be 0xc4 because its TopicType has no key.

• BuiltinParticipantVolatileMessageSecureWriter has EntityKind 0xc2 but it should be 0xc3 because its TopicType has no key.

• BuiltinParticipantVolatileMessageSecureReader has EntityKind 0xc7 but it should be 0xc4 because its TopicType has no key.

*Correct EntityId_t for the builtin writers and readers of ParticipantStatelessMessage and ParticipantVolatileSecureMessage *

See Issue description