Add development info to readme
the Global Zone port forward runs through collision detection

Turns out the Vagrant provides a built-in way to register new
port forwards. By running this code early enough, it shows up in
the list of port forwards that Vagrant will automatically correct
in case of port conflicts.

- use VMConfig#network to register gz_ssh port forward, instead of
  hacking env[:forwarded_ports]
- [resolves #5]
Stop zone before vagrant attempts to halt

- fyi: halting the global zone still takes forever
- todo: ensure that vagrant up and resume work correctly
- [refs #13]
start zone on vagrant up

When a machine is powered off, zones may not start when it
is started with another `vagrant up`. For this reason, let's
attempt to start a zone if it's not already started.

- [refs #13]
Only install gz vnic if we actually are in a gz

create_gz_vnic action seems to run twice, once when the VM
initially comes up and once after our custom hooks all run.
By the time this second one runs, Zonegate is running and the
capability actually runs in the zone. It's unclear why this
was not failing before.
Move zone creation into Zone namespace

- Move action to action/zone/create
- Move capability to cap/zone/create
You can pry if you want to

PRY=1 before bundle exec'ing vagrant in order to require
pry in the ruby environment.
Zone#running? method
Wait for zonegate to start in cap/zone_gate/enable
Disabling zonegate disable nat rules

zonegate wmf method script now looks at $SMF_METHOD
to start or stop processes. When stopping processes,
iterate through zones and disable nat rules.

[resolves #6]