Make enforcer more deterministic.

When in a situation where two keys can make a transition but not both, the final result depends on the order of keys returned by the database. This is not an operational bug. One key is not better than the other and there is no intrinsic order. In our tests however this can be a problem.

We either need to

• order the DB queries, but this may affect ALL queries and therefore slow.
• order specific database structures. (keydata)
• build our tests to handle this.

Currently I changed the enforcer.timeleap.mongrel test in such a way that no two CSK rollovers within a zone can happen at the same time.