Native "Confirmation Dialog" for Destructive Actions (Delete Row)

**Summary**
Developers need a built-in **Confirmation Modal** (Pop-up) option within the Action Editor, specifically for destructive actions like "Delete Row". Currently, to prevent accidental deletions, developers are forced to build entirely new "Overlay Screens" or "Edit Forms" with complex visibility logic just to ask the user *"Are you sure?"*. This is an enormous amount of work for a standard UI pattern.

**Current Problem**
* **High Development Effort for Simple Safety:** To create a "Safety Check" today, a developer must: create a new generic screen, pass the Row ID, design a text component ("Are you sure?"), add two buttons (Yes/No), and configure the actions. This takes 20 minutes for something that should be a single checkbox.
* **Accidental Data Loss:** Without this workaround, the "Delete Row" action triggers instantly on click. Users frequently delete data by mistake (fat-finger error) because there is no friction or warning.
* **Overkill UI:** Using a full "New Screen" or "Form" just to show a warning is bad UX; it feels heavy and slow compared to a lightweight system modal.

**Examples/Scenarios**
* **Deleting a File:** As shown in the attached example, deleting a document should trigger a pop-up: *"Are you sure you want to remove Research.docx? This cannot be undone."*
* **Archiving a Project:** When a manager clicks "Archive", they should confirm the action to prevent closing an active project by mistake.
* **Canceling an Order:** A critical action that requires a "double-check".

**Why This Matters**
* **Data Integrity:** drastically reduces accidental data loss.
* **Developer Velocity:** Replaces complex workaround logic with a simple native setting.
* **Standard UX:** Every modern application has confirmation dialogs for destructive actions.

**Suggested UX**
* **Action Settings:** Inside the Action Editor (e.g., when configuring a Button -> Delete Row), add a toggle: **"Require Confirmation"**.
* **Customization:** When enabled, allow the developer to define:
* **Title:** (e.g., "Delete File?")
* **Message:** (e.g., "This action is irreversible.")
* **Confirm Button Label:** (e.g., "Yes, Delete") - ideally with a "Destructive/Red" style option.
* **Cancel Button Label:** (e.g., "Cancel").
* **Behavior:** When the user clicks the button, the Native Modal appears. The actual Action (Delete) only runs if "Confirm" is clicked.