Scenario DatastoreAccess tests incorrectly access to Yugabyte nodes

[mickmis]

Describe the bug
The test scenario DatastoreAccess attempts to validate that the communication between Yugabyte nodes are: 1) authenticated, 2) encrypted, 3) encrypted using a modern enough scheme.

Currently checks 1) and 2) are made against the client ports of Yugabyte using psycopg. This is incorrect as we need to validate the internodes communication, not the client one.

Relevant files where this is implemented:

• https://github.com/interuss/monitoring/blob/ca9f01d53d95cd06e07b44277c5d0ca3a82e6bb9/monitoring/uss_qualifier/scenarios/astm/dss/datastore_access.py
• https://github.com/interuss/monitoring/blob/ca9f01d53d95cd06e07b44277c5d0ca3a82e6bb9/monitoring/uss_qualifier/resources/interuss/datastore/datastore.py

Possible solution
Implement the checks on the internodes communication port (7100 or 9100), possibly using the approach of 3), i.e. checking the raw bytes.

[mickmis]

Yugabyte uses the 'HBase' RPC communication protocol (https://gruchalski.com/posts/2022-02-12-a-brief-look-at-yugabytedb-rpc-api/). Unlike gRPC it does not use HTTP2. As such we might need to write some simple client to establish a connection with the nodes to validate the requirements.