Add additional resource and system metrics to the collection and output of validator-info

[WadeBarnes]

The Technical Verification Script collects and analyses node resource and and system information in order to determine and report on a given node's level of compliance. To facilitate continuous health, diversity, and compliance monitoring the collection and analysis of the data should be separated. The metrics should be collected and reported by the node itself through validator-info, and the analysis should be performed within hyperledger/indy-node-monitor as discussed here; hyperledger/indy-node-monitor#24 (comment). This would allow an organization to develop their own set of compliance metrics and write an indy-node-monitor plugin to analyze and report on a given node or network's level of compliance based on those rules.

As such the scope of this ticket would be to incorporate the metrics collected by the Technical Verification Script into validator-info so they become more readily available for continuous monitoring solutions.

While designing/implementing give some thought to any additional metrics that would support continuous security monitoring as discussed here; hyperledger/indy-node-monitor#24 (comment)

All information should be included in the output of validator-info on the node itself, and authenticated calls to the get-validator-info transaction.

This is to address the discussions regarding incorporating the collection of the additional data analyzed by the Technical Verification Script, in order to facilitate continuous compliance monitoring; hyperledger/indy-node-monitor#24 (comment)

Requirements:

• Ensure technical policies already enable the extraction of additional metrics for validator-info #1672
• Determine ACLs on who is allowed to request, receive and store additional metrics for validator-info #1673