DDSIRTP23 — Builtin Interparticipant Channel should have DataReader reliability kind BEST_EFFORTS

Currently it is RELIABLE. The problem is that this channel is used to send the Liveliness assertions. Being reliable if one is lost, future assertions cannot make it through even if they are written by the DataWriter. Rather it has to wait for the repair packet which depends on timing for HeartBeat and repair which may be longer than the assertion period.

Since the assertion message is small, it is more efficient to send it faster than rely on faster heartbeats and ACKNACKs.

This change would be backwards compatible since the DataWriter would still have reliability kind RELIABLE.

*Add Flags to the BuiltinEndpointSet to Facilitate Communication of Configuration Options *

It is useful to be able to configure the builtin endpoints and then communicate the configurations. A new PID has been defined that will allow communication of these specific configurations. One of the new flags will be used to communicate the Reliability kind of the inter-participant DataReader.