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
My thinking was that aligning container naming with dns naming is a useful default. And piggybacking on `--name` means users won't have to remember another noun.

There is actually a problem with this: you can't run two containers with the container same name on the same host, but you may want to run two containers with the same DNS name on the same host.

So I guess we do need to have our own now :(