ASACORE-905: Remove dependency on NameOwnerChanged signals for TCL

Ask the routing node to filter the NameOwnerChanged signals it sends to
this client to the unique names that are interesting to the client.
This change should reduce the number of redundant NOC signals sent to TC apps.

Part 1: move processing of some messages into AJ_UnmarshalMsg
This change allows the session state messages to be processed by
the system code before the application code. Those messages are
unmarshaled, processed, and then reset to retain any legacy behaviors.

Part 2: remove session message processing code from AJ_BusHandleBusMessage
The processing now takes place at the end of AJ_UnmarshalMsg, remove this old code.

Part 3: Use AJ_GetRoutingProtoVersion to add a filtered signal rule (or not.)
For older routing nodes: keep the original NameOwnerChanged rule
For new routing nodes: ask for a filtered NameOwnerChanged signal.

This keeps the session cleanup code the same, because the leaf node
will receive NOC signals that correspond to authenticated peers.


Change-Id: I63d3f3188a65cb5b67e1e871024ea5c16f1458a7
Signed-off-by: Chris Pezzee <cpezzee@qce.qualcomm.com>
Merge remote-tracking branch 'origin/feature/asacore905'

Change-Id: I458dc8fe76901058e0513b3e2e89e875052e34b5
Signed-off-by: Chris Pezzee <cpezzee@qce.qualcomm.com>
Merge "Merge remote-tracking branch 'origin/feature/asacore905'"