Implement durable kind API

[FUDCo]

This implements the durable kind API (though not the rest of the baggage machinery) per #4495

In particular, we provide the new VatData function makeKindHandle to produce durable (and storable) handles that may be used to associate durable kinds with their implementations. At least, that is what it is called until we change the name again.

Closes #4495

[erights]

New functions must be arrow functions.

[erights]

All new functions must be arrow functions.

Aside from that, looks good to me!

[erights]

LGTM, thanks!

[warner]

This can probably land with just the recommended harden calls.

Please think about the kindIDID-on-DB issue, it may be that we can't address it properly until #4730 has a solution, in which case we could fix both at the same time. I guess at least add a note to the let kindIDID line to remind us that in-RAM counters are going to be trouble.

Consider the "use 'defineDurableKindto define theKindHandle` kind" thing, but I wouldn't consider it mandatory.

[warner]

I'm a bit bothered by the idea that this will differ from one vat to another, depending upon when that vat happens to make it's first handle.. I think that's going to make debugging harder. It overlaps with a similar concern about the IDs used for the standard virtual collections.

Is there any good way to make these values be the same for all vats?

[FUDCo]

I don't think there's a good way, though it's certainly quite doable. The reason I did it the way it works now is that many vats don't need these things at all and so they only get created/allocated the first time somebody asks for one. We could pre-allocate these for every vat, which would yield uniformity, but then we'd be carrying the overhead (mostly in the form of junk database entries, which I've found to be its own source of confusion when debugging) in all the places it's not used. In practice I haven't found the variance of the IDs from one vat to another to be a debugging issue, since if you are looking at things at that low a level you see the record of the ID allocations along with their use. And of course you typically debug in the context of a single vat and in that context the IDs stay the same from one debug run to another.