Fix memory read after free bug found via valgrind

members.role could be read after free in iterate relations in non-slim
mode
The strategy for organising the db by geographic order was flawed

Remove the "Order by way" method and make it configurable if we
don't reorganise the rendering tables by geometry, CLUSTER on the
gist index of way, or CLUSTER on a new geohash index