Move Pre and Post Deploy Hooks to composable roles

Currently we have a bunch of "hooks" that operators can use both pre and post deployment, e.g.

OS::TripleO::NodeExtraConfig
OS::TripleO::NodeExtraConfigPost
OS::TripleO::Tasks::ControllerPrePuppet
OS::TripleO::Tasks::ControllerPostPuppet

However it becomes increasingly difficult to figure out what deployment hook is the right one to use, when it is run, and what nodes it's run on. On top of this, you may have multiple environment files (especially those implementing plugins from vendors) all trying to overwrite the same thing in the resource_registry.

Instead what we can do is move towards having the pre and post deployment "hooks" implemented as composable roles instead (included by default in our default node sets). This will make it a lot clearer to operators where exactly in the deployment process they are run, and allow them to tweak the roles file to work with these how they like. Likewise, it will allow us to stack composable roles for our own work combined with vendor/existing work more easily