Add sync tests

[DyrellC]

Description

A nightly test for checking the sync speed of a node. A number of nodes is spun up in TIAB. The first node: nodeA, will be used as the baseline sync along with another synced node nodeB, while the last (nodeC) will be loaded up without a db or snapshot files. The test will then listen to the nodes to register changes in the latestSolidSubtangleMilestone until all nodes are synchronised. It generates a log and syncing graph for each node syncing, and puts them into the SyncOutput directory. Once the tests are finished, the cluster is torn down. To run the test, the user will need to have a kubernetes access token available in their ./kube/config. They will also need to be running the test with root access, as there are packages that need installing for the test utilities.

Nightly-Tests
   |__ Sync-Tests
       |__ createCluster.sh            // Bash command for starting a TIAB cluster and running scans
       |__ zmqTest.py                  // Uses ZMQ to listen for node sync updates and clock the sync time 
       |__ config.yml                  // Holds the configuration for the TIAB 
       |__ SyncOutput                  // Output files for sync test
          |__ Date
             |__  *.log
             |__  *.png
    |__ Utils                           // Tools for tests (Intended to be used by all python Nightly's)
       |__ *-tools.py                                 
    |__ setup.py                        // Dependencies for Nightly test tools 

Motivation

To monitor the sync speed changes on nodes running the latest features and changes on IRI

Tested

zmqTest.py tested on locally running nodes, createCluster.sh tested with kubernetes configuration file present.

Note: Kubernetes started acting up at the end of the testing phase for this, so I'll have to run the tests again once the service is back online to confirm the test is working as intended. This test also does not have the inclusion of a sync from local snapshot files yet, as there is only one set available on dbfiles.iota.org in testnet, and it's too far ahead for use here. We may need to throw one up in a bucket or onto the dbfiles from the nodeB db in the default configuration, and have it sync that way? Will discuss with the team next week.