Enhance User Confirmation on Workflow Definition Deletion with Affected Entities List

### Description:
When attempting to delete a Workflow Definition, it is crucial for users to be fully aware of the implications of this action, particularly regarding the deletion of related workflow instances and the potential impact on other workflow definitions. Currently, the deletion process does not provide sufficient warning or detail about these consequences.

**Proposed Enhancement:**
- Implement a confirmation dialog that appears when a user initiates the deletion of a Workflow Definition. This dialog should:
- Warn the user that deleting a workflow definition will also remove all associated workflow instances, including both running and completed instances.
- Inform the user if other workflow definitions might be affected or break due to the deletion of the current definition.
- Display a list of affected entities, such as the names or IDs of the workflow instances and any dependent workflow definitions. This list helps the user understand the full impact of their action.

**Objective:**
The goal is to enhance the user experience by providing comprehensive information that allows users to make informed decisions about deleting workflow definitions. This feature will prevent unintended consequences and ensure users are aware of the cascading effects of their actions.

**Requirements:**
- Update the workflow deletion process to include a confirmation dialog with detailed information on the impact of the deletion.
- Ensure the dialog lists all affected workflow instances and any dependent workflow definitions.
- Test the implementation to verify that users receive accurate information about affected entities before confirming deletion.

This enhancement will significantly improve clarity for users, helping to avoid potential issues that can arise from inadvertently deleting important workflow definitions and their associated instances.

The issue names no files, tests, or entry points. Start by locating the Workflow Definition deletion action and its existing confirmation dialog, then trace how related instances and dependent definitions are identified. Done means the dialog accurately warns about all listed impacts and is covered by tests for affected and unaffected definitions.

Written by the indexing model from the issue text.