compile and deploy should respect different platform versions for different envs
Currently leap compile
will use the platform that is checked out without warning if some environments have used a different version before.
leap deploy
warns instead:
The platform is pinned to branch 'master' by the `platform.branch` property in provider.demomail.json, but the current branch is 'version/0.9.x' (for directory '/home/azul/code/leap_platform')
Ideally both would create a temporary clone of the pinned branch instead and deploy different versions of the platform if desired. So that a leap deploy webapp
can succeed even in a mixed set of environments and a leap compile
will not change version info in ways inconsistent with the previous setup.