Walkthrough demonstrating weave 1.0 features

@rade says:

One way to elucidate all the features we'd like to be part of Weave 1.0, is to imagine what a demo transcript would look like.

Headings denote the new features we are demonstrating in that part of the transcript.

The demo highlights features with minimal effort; for a really compelling demo it may be advisable to re-cast everything in terms of an imaginary system somebody is putting together.

We focus on new features. All these are additive, i.e. all existing functionality is still present but may require slightly different CLI commands than present. Nothing should rely on new features or changes to Docker.

Key theme: ultimate simplicity for the common case
I like the opt-out of DNS, not so sure about co-opting `name`. My inclination is that people will want to have their own container naming scheme. This is especially a difficulty later on when the name has a special meaning that's different to the docker argument.

Is there anything (aside from proliferation of nouns) stopping us having a different argument (and thereby letting someone supply a docker name *as well*)?