[FEATURE] Respect "SurfCaptain.json"

[t3easy]

For versioning a deployment configuration of a project a "SurfCaptain.json" in the project could hold the configuration.
So the dev can change the build steps within the project -> commit -> build and deploy with new settings/steps/whatever.

[ervaude]

As of now the steps (tasks) that are performed when deploying e.g. TYPO3 CMS are defined in the Application class (see: https://github.com/lightwerk/SurfRunner/blob/master/Classes/Lightwerk/SurfRunner/Domain/Model/Application/TYPO3/CMS/DeployApplication.php).

I dont think it is very likely that you will have surf deployments of the same application but with different task sets. If I understand you correctly this is what you are aiming for?