[WIP] method based deployment

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
* [ ] - Heroku method
* [ ] - New tests with passing current tests