[WIP] method based deployment

[tamagokun]

This is a rather large re-vamp of how deployment stacks are built.

Not ready

Deployments with Pomander have a strict release/no-release structure with some options one of which being scm to help offer a more flexible means to deploy for all projects. Problem is there is no way to break out of this structure and create deployment paths for other things (i.e. Heroku, Docker)

This new way allows that to happen..

All deployment related tasks are driven by a Method object. The method ultimately controls exactly how a deployment works. The base Method class implements the standard release / no-release structure for deploying, rolling back, cleanup, finalize, etc. There are stubbed methods for setup_code and update_code that you can sub class and customize to your needs, or just implement all new methods.

Breaking changes:

This release will introduce some potential breaking changes for anyone that used the $app->env->scm object. That object is now replaced by method.

• - Git method
• - Subversion method
• - Rsync method
• [ ] - Heroku method (later)
• - New tests with passing current tests

[tamagokun]

This will also take care of #31 #47

[tamagokun]

For Heroku deployments Pomander needs to be able to trigger a heroku task after composer installs all of its deps:

This can probably be achieved by means of a Composer plugin: https://getcomposer.org/doc/articles/plugins.md

After the plugin is loaded, pom heroku