Controller filters can shortcut request lifecycle by returning a Response


  * If a before filter returns it, both the action and the after filters will be skipped (as well as any remaining
  * If an after filter returns it, any remaining after filters in the block will be skipped.
  * There is no way for the action result to skip the :after filters.

Closes #21
Signed-off-by: Josep M. Blanquer <blanquer@rightscale.com>
It won't once we change the setup! semantics to be more appropriately. For now we moved the sub-stages from the validate to the initialize (out of the setup! method)