Add time-range filtering to support bundle log collection

[smklein]

Adds a bundle-wide time-range concept that flows from the omdb CLI down through BundleDataSelection, the support-bundle-collection mechanism, the sled-agent API, and into sled-diagnostics, where the per-file mtime gate is applied to archived and extra log files (current logs are always included regardless of the window).

Highlights:

• New BundleTimeRange { start, end } type in nexus_types::support_bundle. The window is bundle-wide: a single BundleDataSelection::time_range field, applied to both host-info log collection and ereport queries.
• BundleDataSelection::all() defaults to a 7-day window — same default as ereports already had; logs gain the same cap where they had none.
• Sled-agent API gets a new VERSION_ADD_LOG_TIME_RANGE (v38) that reshapes SledDiagnosticsLogsDownloadQueryParam: max_rotated becomes optional; start_time/end_time are added.
• sled_diagnostics::LogsHandle::get_zone_logs keeps oxlog's date_range: None and applies the time gate explicitly inside get_zone_logs_inner. Files with unknown mtime are over-inclusively kept.
• Sim sled-agent gains a SimLogEntry injection surface so tests can construct synthetic log files with controlled mtimes; default behavior (no entries injected) remains an empty zone list.
• omdb support-bundle collect gains --since <duration> and --until <duration> flags (humantime, both relative to now).
• Persistence: schema v257 adds bundle-level support_bundle_data_selection_time_range and the FM equivalent, keyed by bundle / sitrep+request id. Existing per-category time columns on the ereports tables are migrated and dropped.
• Integration test in nexus/tests/integration_tests/support_bundles.rs injects entries on the sim sled-agent at 30 m, 6 h, and 30 d ago, collects with a 24 h window and a 7 d window, and asserts only the recent entries land in the bundle.

Fixes #10372.

[smklein]

Query parameters are apparently supplied in alphabetical order, which is why "end time" comes before "start time" 🫠