MON_GET_CONNECTION to show the SSL protocol information for DPF

Please enhance MON_GET_CONNECTION to show the SSL protocol information for DPF when the client connects to
a non-catalog partition. This was highlighted in TS020092882 case "DPF-Non-Catalog-Node-Connection-Is-Not-SSL"
This is useful to show correct SSL connection information.

db2 "select client_protocol, client_ipaddr, member,system_auth_id from table( mon_ge
t_connection(NULL, -2)) with ur"

MON_GET_CONNECTION won't show the "gateway" side connection information. It only shows the end part of the connection chain.
The end part of the connection seems fine but we need to check whether mon_get_connection would return such information.

The SET CLIENT CONNECT_MEMBER <node number> parameter and the DB2NODE environment variable allow the client to connect to a partition that is not part of the host to which it is configured to connect. There are two separate connections established in this case:

The connection between the client and the host to which it is configured to connect.
The connection between the host and the partition specified in the CONNECT_MEMBER parameter.
The second connection is referred to as a hopped connection.
TLS can be enabled for both connections, but hostname validation can only be enabled for the first connection.

If there are multiple logical partitions on the destination host and the partition being connected is the one not listening to the network, there will be a third IPC connection to the desired partition.

Each host has a node in which the port is being listened. Usually, it is the node that comes first on db2nodes.cfg. For instance:

This is my db2nodes.cfg:

0 host1 0
1 host1 1
2 host2 0
3 host2 1

Whether I need to connect to node 3 (export DB2NODE=3), this is the connection path:
                                          1                                                                       2

client --( IPC to local node )--> NODE 0 --( TLS to node on remote host )--> NODE 2 --( IPC to local node )-
3 -> NODE 3

In order to reach NODE 3, we connect to NODE 0 (1) then the connect to the remote host via (2), which contacts the desired logical partition using IPC (3).

export DB2NODE=6
db2 terminate
DB20000I  The TERMINATE command completed successfully.
db2 connect to nt120005

  Database Connection Information

Database server        = DB2/LINUXX8664 11.1.4.7
SQL authorization ID   = MASAKI
Local database alias   = TESTNY

db2 "select client_protocol, client_ipaddr, member,system_auth_id from table( mon_get_connection(NULL, -2)) with ur"

CLIENT_PROTOCOL CLIENT_IPADDR                                                                                                                    MEMBER SYSTEM_AUTH_ID
--------------- -------------------------------------------------------------------------------------------------------------------------------- ------ --------------------------------------------------------------------------------------------------------------------------------
LOCAL           -
1 MSDB2
TCPIP4          -
1 MASAKI
LOCAL           -
3 MSDB2
LOCAL           -
8 MSDB2
LOCAL           -
9 MSDB2
LOCAL           -                                                                                                                                    10 MSDB2
LOCAL           -
7 MSDB2
LOCAL           -
2 MSDB2
LOCAL           -
4 MSDB2
LOCAL           -
5 MSDB2
LOCAL           -
6 MSDB2
SSL4            10.207.203.180
6 MASAKI

 12 record(s) selected.