[Feature Request]: [REFE] Add native Retry and Retry Delay options to Workflow Actions

### What would you like to happen?

Current Behavior:
Currently, Workflow actions (such as Pipeline, Workflow, SQL, etc.) do not have a native mechanism to automatically retry upon failure. To implement a retry logic (e.g., "retry 3 times every 5 minutes"), users must manually design complex loops using 'Check' actions and 'Delay/Wait for' steps, which clutters the workflow canvas.

Proposed Feature:
Add a new tab called "Retries" or "Error Handling" to the standard Workflow Action dialog. This tab should include:

Enable Retry (Checkbox): To activate the mechanism for that specific action.

Number of Retries (Integer): How many times the action should be re-executed before propagating a "Follow Error" result.

Retry Delay (Integer/Time): The amount of time the workflow should wait before the next attempt.

Delay Scale (Dropdown): Options for Seconds, Minutes, or Hours.

User Story:
"As a data engineer, I want to configure an action to retry automatically in case of a transient failure (like a network timeout or locked database) without having to build a manual loop in my workflow or restart the entire process."

Goal:
The workflow should "hold" its execution at that specific stage during the retry attempts, maintaining a cleaner and more professional orchestration logic.

### Issue Priority

Priority: 3

### Issue Component

Component: Hop Gui

Start by locating the Hop GUI standard Workflow Action dialog and the execution path for actions such as Pipeline, Workflow, and SQL. Define how retry count, delay value, and seconds/minutes/hours scaling interact with a failed action. Done means users can configure retries for an individual action, wait between attempts, and receive a Follow Error result after retries are exhausted.

Written by the indexing model from the issue text.