Filter support bundle log collection by zone type

[smklein]

Stacked on #11190.

Support bundle log collection can now be filtered by zone type
(#10372). BundleZoneType names every category of zone a sled can
hold logs for: one variant per Omicron zone-name prefix, plus the
global zone, the switch zone, and instance (propolis) zones. A
bundle's host-info selection carries a ZoneSelection alongside its
sled selection: all zones (the default, preserving today's behavior)
or only zones of specific types.

POST /v1/system/support-bundles
{
  "user_comment": "nexus crash loop on BRM42",
  "data_selection": {
    "data": {
      "type": "explicit",
      "host_info": {
        "zones": { "type": "specific", "types": ["nexus", "cockroachdb"] }
      }
    },
    "start_time": "2026-08-29T00:00:00Z"
  }
}

A few design points worth calling out:

Zone types are derived from zone names, not from ZoneKind. The zone
list comes from on-disk log directories, which outlive the zones
themselves, so the name is the only typing available; and zone names
cannot distinguish boundary from internal NTP zones, so ntp covers
both. A From<ZoneKind> impl plus a coverage test over
ZoneKind::iter() keep the classification exhaustive as zone kinds
are added.

Filtering happens in the collector, after listing a sled's zones and
before requesting their logs, which is where the cost lives: each
download makes the sled-agent take ZFS snapshots and assemble a zip
file. The sled-agent API is untouched.

The selection is persisted as a TEXT[] of the enum's stable strings
on both host-info selection tables (the bundle's and the FM
support-bundle-request twin), mirroring how sled selections are
stored. Existing rows backfill to "all zone types". Reading back an
unrecognized stored string is an error rather than a silent drop.

omdb support-bundle collect and omdb nexus support-bundles create
grow a repeatable --zone-type flag.

Test coverage

The first commit unit-tests the classifier: every zone-name shape,
the prefix-shadowing pairs (crucible/crucible_pantry and the
clickhouse trio), malformed and unknown names, plus the
ZoneKind::iter() coverage test and a test pinning that the serde,
persistence, and FromStr string forms agree. Builder composition
(zone types surviving a later sled selection and vice versa) is
covered as well.

The second commit adds a datastore test round-tripping selections
with specific zone types and with an empty type set through the
bundle tables, extends the FM sitrep round-trip test with a zone-type
selection, and adds a data-migration check verifying pre-existing
host-info rows backfill to "all zone types" and that the new CHECK
constraint rejects inconsistent rows.

The third commit's integration test injects a log for one zone of
each name shape into a simulated sled-agent and inspects the
collected archive: no selection collects every zone (including one
with an unclassifiable name), a type subset collects exactly its
matches, and an empty type set collects no zone logs at all.

The fourth commit extends the explicit-selection API round-trip test
with a zone-type selection, which also pins that the view reports the
set in canonical order, and the existing proptest now round-trips
arbitrary zone selections through the API type.

The fifth commit is covered by the omdb usage tests; the flag error
path (naming zone types while excluding host-info) is exercised by
the shared selection-building code.