Node timing

[paigerube14]

This is adding in the ability to add AffectedNode timing to a list that we can track in the telemetry and other output.

This tracks the amount of time that is taken for the cloud provider to stop/start the node, and the amount of time after the node from the cloud side is stopped/started what is the time the node is in not ready/ready state.

Needs to go in after krkn-chaos/krkn-lib#143

Any suggestions on how to make this not touch as many files?

New telemetry section will look like this for a stop/start scenario

          "affected_nodes": [
                    {
                        "node_name": "ip-*.us-east-2.compute.internal",
                        "not_ready_time": 0.0,
                        "ready_time": 24.439035892486572,
                        "unknown_time": 0.15461111068725586,
                        "stopped_time": 136.35135626792908,
                        "running_time": 15.249454021453857,
                        "terminating_time": 0.0
                    },
                    {
                        "node_name": "ip-*.us-east-2.compute.internal",
                        "not_ready_time": 0.0,
                        "ready_time": 23.62007188796997,
                        "unknown_time": 0.15206694602966309,
                        "stopped_time": 166.52288508415222,
                        "running_time": 15.330392122268677,
                        "terminating_time": 0.0
                    }
                ],

[chaitanyaenr]

Tested different combinations and the reporting is working as expected. Working node scenario configs:

• one action - node_stop_start_scenario targeting one instance count
• one action - node_stop_start_scenario targeting multiple instance count

Scenario with multiple actions is failing to report the metrics due to a bug in the node-scenarios code base outside this PR: #749

[chaitanyaenr]

Leftover logging from the test runs, need to remove it.