Track changes of presto cluster and provide hash of current configuration

[kokosing]

It would be nice to track all the changes to presto cluster. So user can:

• see history of configuration changes (like change in node.properties file or new presto version installation)
• retrieve a hash (or id) of configuration, so she/he knows that nothing changed in cluster if no configuration or presto version changed

It would be super-helpful for benchmarking or maintaining presto cluster in case where is some performance degration is observed (or new query failures) it is easy to say what have changed in cluster and narrow a search space in order to find a root cause of an issue.

CC: @pnowojski