DDS — Ref-109 Destination_order_should_be_request_offered

In order to support the BY_SOURCE_TIMESTAMP setting the DataWriter
needs to take appropriate actions (e.g. embed timestamps). Therefore
the DESTINATION_ORDER QoS should follow the same request/offered
pattern other QoSs do.

**PROPOSAL**

Modify the QoS table in section 2.1.3 and add DataWriter as in the
"Concerns" column for DESTINATION_ORDER. Also replace with "Yes" in
the "RxO" (request/offered) column.

Add a paragraph to section 2.1.3.11 stating the request/offered
compatibility as follows:

The value offered is considered compatible with the value requested if
and only if the inequality "offered kind >= requested kind" evaluates
to 'TRUE'. For the purposes of this inequality, the values of
DESTINATION_ORDER kind are considered ordered such that
BY_DESTINATION_TIMESTAMP < BY_SOURCE_TIMESTAMP.

see below