Adds elasticsearch[:skip_restart_on_update]

Allows for more control over when ES nodes restart. Currently, we use Chef search to manage nodes, which means the IP addresses of other nodes are in the configuration file for each ES node. If we add a new node to the cluster, Chef writes the new IP and restarts ES on all the nodes. If we get unlucky with the timing of our Chef runs, too many nodes would go down.

This setting will prevent changes to the configuration or logging files from restarting ES.