fix(events): order entries by insertion order when selecting

[rvagg]

Fixes: #11823

Replaces: #11829

I went down the rowid rabbit hole that @Stebalien mentioned in #11823, in https://www.sqlite.org/lang_createtable.html#rowid:

The rowid value can be accessed using one of the special case-independent names "rowid", "oid", or "rowid" in place of a column name.

So, it's there already, let's use it! This requires no migration, and just sorts on the way out. The example message I had in #11823 now looks like this from GetActorEventsRaw:

  "entries": [
    {
      "Flags": 3,
      "Key": "$type",
      "Codec": 81,
      "Value": "bnNlY3Rvci11cGRhdGVk"
    },
    {
      "Flags": 3,
      "Key": "sector",
      "Codec": 81,
      "Value": "GScT"
    },
    {
      "Flags": 3,
      "Key": "unsealed-cid",
      "Codec": 81,
      "Value": "2CpYKAABgeIDkiAg8pxbycLUKlq7v8IZyXva5vs6aSxy9/mz5t2ygXvZjAw="
    },
    {
      "Flags": 3,
      "Key": "piece-cid",
      "Codec": 81,
      "Value": "2CpYKAABgeIDkiAg8pxbycLUKlq7v8IZyXva5vs6aSxy9/mz5t2ygXvZjAw="
    },
    {
      "Flags": 1,
      "Key": "piece-size",
      "Codec": 81,
      "Value": "GwAAAAgAAAAA"
    }
  ],

And, from what I can see, $type is coming first on all of them.

I think it's that simple. Will be testing more today with my tooling to make sure my assumptions hold.

[rvagg]

important test change here - $type should be first

[rvagg]

important test change here - this is a sector activation with 2 pieces, we're asserting they are strictly in this order so the piece-cid + piece-size pairings are intact. Note also the require.Equal below (I've also replaced all the require.ElementsMatch elsewhere that operate on event elements).

[Stebalien]

Maybe we should do a migration where we rename _rowid_? Can happen later.