Fix table ordering to respect tableDefinitions array order

[Copilot]

Tables were displayed in a grouped order (all prefix tables, then all catch-all tables) instead of respecting the user-specified order in CoverageFromAzureStorageOptions.tableDefinitions.

Changes

• Modified splitManifestByTables() to process tables in their original definition order
• Pre-compute prefix matches to identify scenarios that match any prefix table before iteration
• Updated catch-all logic to exclude scenarios matching any prefix (regardless of table order) while still only consuming unassigned scenarios

This preserves the user's intended table ordering while maintaining correct catch-all behavior: catch-all tables only receive scenarios that don't match any prefix table in the definition array.

Example

const tables: TableDefinition[] = [
  { name: "Data Plane", packageName: "azure", prefixes: ["dataplane_"] },
  { name: "Other", packageName: "azure" },  // catch-all
  { name: "Management", packageName: "azure", prefixes: ["mgmt_"] },
];

Before: Tables displayed as Data Plane → Management → Other
After: Tables displayed as Data Plane → Other → Management

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Tables do not seem to be sorted based on the tableDefinitions</issue_title>
<issue_description>The table display should respect the CoverageFromAzureStorageOptions tableDefinitions ordering.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Tables do not seem to be sorted based on the tableDefinitions #9061

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

No changes needing a change description found.