Fixes #8, "Allow control over which `GraphState` operations are depicted by server". Enables use of multiple visualized GraphStates in the same program. Downside -- you have to call `update()` at the end of your program.

Moved that functionality into `abp.GraphState`, so that you can
just run `state = abp.GraphState(nx.Graph(((0,1),)))`, `state =
abp.fancy.GraphState(nx.Graph(((0,1),))` or whatever.

Now you can write `abp.fancy.GraphState(nx.Graph())`.
TODO: make this work for a non-fancy `GraphState`

Very functional, very explicit node names - working so far

To play around with lattices

Conflicts:
	.bumpversion.cfg
	setup.py

Trying to get more sensible defaults for people who like to think about
graphstates rather than circuits.

Repsponse to issue #4: [Link](https://github.com/peteshadbolt/abp/issues/4)

Empty for new

I have written a tonne of tests that compare against A&B's original C++.
Until I can distribute the `anders_briegel` package which implements
that original code, we now skip those tests if we see an ImportError.

TODO: seems a little over-zealous right now ...

Is this going to fix errors with different versions of networkx? I don't
know -- I'm on a plane mate.

- `GraphState.copy()`
- `measure_x` etc.
- `measure(detail=True)`
- Better documentation on `remove_vop` and `act_local_rotation`