Fix test failure caused by differing output order.

This is probably not the right way to go about this; the lack of any ordering on Boundary meant that locally some intersect tests failed due to the ordering of the list being different in the test JSON. So I added ordering to the intersect call (and ordering the JSON) which fixed those failing tests, I don't know if it would be better done by default ordering on Boundary itself.