Looks like nondeterminism in `next(d.iterkeys())` was breaking
consistency with A&B. Next up: switching determinism on or off.

Had a dumb translation error

Some tests are disabled and forcing outcomes does not work

Dunno why it was ever `complex`

Actually happened in previous commit, can't be bothered to amend

It's kinda ghastly at the moment. But lots of obvious improvements.

Added some more terms to clifford.by_name to ease lookup of complex
conjugates

Added GraphState.toggle_edges(), used by GraphState.measure_x

Nearly finished GraphState.measure_x

Made sure that `graph.js` dumps old graphs after use, and ensured that
`examples/stress_test` shuts down the connection after use (don't create millions
of clients).

By default the server echoes messages to all clients.
The fancy.GraphState client was never calling ws.recv()
And hence a buffer was filling up somewhere
And we were hanging.
Adding a ws.recv() fixed the problem.

Got rid of all the debug harness and refactored graphstate.py