Move config.sh|php into separate role to allow quick update for autodeployer

[jamesmontalvo3]

Changes

• config.sh and config.php moved out of base role and into base-config-scripts role
• setbaseconfig.yml playbook created to just update these scripts
• meza setbaseconfig ENV command created for quick update
• Add to autodeployer: update config.sh (and config.php, but that doesn't matter for autodeployer) at beginning of autodeployer to pick up any changes from Secret config (which isn't currently managed by autodeployer). Then again update config.sh after Public config change in case changes impact config.sh.
• Make it so notifications include list of commits involved in all changes.

Issues

• Still open issue: Autodeployer currently does not do a full deploy. It does an incredibly minimal deploy in order to move quickly for testing. Unfortunately to test this easily in production it's better to use the master branch. Since autodeployer is a new feature it's not really breaking anything.

Post-merge actions

Post-merge, the following actions need to be addressed:

• Still need to add autodeployer documentation at https://www.mediawiki.org/wiki/Meza