Ability to Convert/Migrate between Glide Table and Big Table Preserving UI Bindings

**Summary**
Users need a built-in tool to migrate data from a standard **Glide Table** to a **Glide Big Table** (and vice-versa) without breaking existing app screens, actions, and component bindings. Currently, moving to a Big Table requires recreating the table and manually re-linking every single component in the app, which is prohibitive for complex, mature applications.

**Current Problem**
* **The "Success Punishment":** When an app starts with a standard Glide Table (MVP phase) and grows successfully, it eventually hits the row limit (25k+). To scale, the user *must* switch to Big Table.
* **Total UI Disconnect:** Currently, there is no way to "upgrade" the table. The user has to create a fresh Big Table and import data. Because the Table ID changes, every screen, collection, and text component connected to the old table breaks.
* **Manual Rebuild:** Developers are forced to spend days or weeks rebuilding screens from scratch just to point them to the new data source, even though the data schema is identical.

**Examples/Scenarios**
* **Scaling an MVP:** A startup builds an inventory app on standard Glide Tables. Six months later, they hit 25,000 rows. Moving to Big Table effectively means rewriting the app’s frontend logic from zero.
* **Performance Optimization:** A developer realizes a specific table is causing lag and wants to move it to Big Table for better query performance, but cannot justify the cost of rebuilding the UI.
* **Downgrading/Refactoring:** A developer mistakenly started with Big Table but realizes they need specific Computed Columns or instant sync features only available in standard Glide Tables, but is now "locked in" to Big Table.

**Why This Matters**
* **Supports App Growth:** Removes the fear of starting small. Developers can begin with standard tables and upgrade seamlessly when needed.
* **Saves Development Time:** Eliminates hundreds of hours of repetitive work re-binding components.
* **Reduces Churn:** Users hitting row limits are frustrated by the migration process and might look for other platforms instead of upgrading to Big Table.

**Suggested UX**
* Add a **"Convert to Big Table"** option in the Data Editor context menu for a standard Glide Table.
* Include a **Mapping Wizard**: If column types differ slightly, allow the user to map Old Columns to New Columns to ensure data integrity.
* **Preserve IDs:** Most importantly, update the backend reference so that all App Screens and Components pointing to the old table automatically point to the new converted table.