So I can see two cases where ordering the serialization might be useful, based on a quick grep of what uses `db-serialize`:

* event/compile-resource-event-(in)equality - so that comparisons of structured data are predictable (and don't lack idempotency potentially?), the inserts are going to come from unordered json maps otherwise and later comparisons might not reflect the same ordering.
* query/compile-resource-equality-v2 - similar reasons as above but for resource parameter values instead.