Improve the developer experience for LAVA

After switching deployments and instances to use buildout, we should make sure that the developer experience is fantastic: it is easy to set up an instance that uses the trunk branches of all our components, hack on those branches and make releases (whatever that ends up meaning) of the state of an instance.

at best install instructions for releases and trunk dev should be very close, like:

ldt install testinstance lp:~xxxx/lava-manifest/trunk
ldt install testinstance lp:~xxxx/lava-manifest/release-0.1

or
ldt update testinstance lp:~xxxx/lava-manifest/release-0.2

also ability to produce a release (e.g. in form of a "pinned manifest") is available

ldt release testinstance lp:~xxxx/lava-manifest/release-0.3
 (-> i guess this would just produce a pinned manifest ... the developer can then commit that to a manifest branch)

and developers can directly edit the bzr branches used inside the release/trunk version to work on their changes.

easy discoverability of where the dev environment can be found, like:

ldt pwd testinstance
 -> /srv/lava/testinstances/code/current/local/

asac even challenges that we need a special --dev/--production mode ... why not have releases and deve done in the same way just using the commands above? you just use ldt update release-0.3 and you have a good release running. the fact that you can even go and hack on it doesnt really hurt imo. Food for thought

some hacking: http://paste.ubuntu.com/1038368/