* breakout support status table to yaml file
* use k8s versions from new yaml file, based off previous ver
* same as previous commit but based off idx of yaml obj
* trim whitespace from supported k8s vers shortcode
* make verion lists arrays instead of strings
* update shortcode to read yaml data array
* rename support status shortcode to follow naming convention
* make versions in table use new arrays, update reference to support status table
* make each version in yaml file a string
* update header comment, change ext to *.yml to follow repo convention
* use prelim ternary to select k8s versions
* update supportStatus.yml heading comments
* update supported k8s shortcode to use branch name
* initial commit of python support status updater
* add null representer
* use lambda for quoted representer
* put back master population off idx 1, update comments
* working stdout version complete: use flow style for version list keys
* prepend yaml with header comments, cleanup script
* perform version check, default write errors are more helpful
* add copyright and license info
* linter has some weird tastes
* this is 100% worse but if it makes the linter happy
* call update_support_status.py from within create version
* update version matrix path since script ran from repo root
* use yq for updating the version support matrix instead of PyYAML
Skyler Spaeth
Martin Taillefer