Enhancement to Generalize config.yaml settings

[roobyz]

Idea: Treat "Installation files" like Cattle

Enhanced the config.yaml file to centralize the initial configuration settings onto one file and avoid having to manually update the installation files. Added and relocated functions to functions.sh. Corresponding updates to setup.sh, and setup.js were made to correctly process the config.yaml.

Benefits:

1. Centralized configuration settings are leveraged by jk to systematically generate the footloose.yaml and machine.yaml files.
2. Separate node settings for control plane and worker nodes.
3. Ease of updating to latest software releases

The parse_yaml() function, reads the whole config.yaml file and assigns each value to variables created using the yaml keys (e.g. "config_" + key1 + key1.1 + key1.2...). Credit for parse_yaml() to Stefan Farestam via Stack Overflow.

Updated software release versions in the config.yaml to the latest supported versions where older releases where no longer supported. To ensure that stale data doesn't hang around, added rm -f machines.yaml footloose.yaml to cleanup.sh