Switch sort order for metadata table entries

Currently, when a table is created it uses a one-up counter for its table name. This means that a workload that creates new tables end up putting all that work on the same metadata tablet.

**Describe the solution you'd like**
Switch the sort order of the metadata table to use the least significant bit of the tableID.

This would spread the new tables metadata entries across multiple metadata tablets while still allowing each table section to be ordered.

Start by tracing metadata table creation and how tableID values determine metadata-table sort order. Confirm that the least significant bit distributes new metadata entries across multiple metadata tablets while preserving ordering within each table section.

Written by the indexing model from the issue text.