[Core feature] Allow Flyteadmin to force terminate an execution

[RRap0so]

Motivation: Why do you think this is important?

With the work done in https://github.com/flyteorg/flyte/issues/5786 it was raised that a Workflow Execution can stay dangling if Flyte Propeller is having problems.

Flyteadmin should support a force flag so it knows that it should remove the execution instead of waiting to be garbage collected by FlytePropeller. This should make management of Workflows easier than having to go to the kubernetes cluster and removing them using kubectl.

On the Flyteadmin side this is now covered by the following PR. Additional PRs are necessary to implement this features in the Flyte clients (flytectl, flyteconsole).

Goal: What should the final outcome look like, ideally?

Both flyteconsole and flytectl are able to pass a force flag to Flyteadmin indicating that Flyteadmin should remove the execution/CRD from the kubernetes cluster.

Describe alternatives you've considered

N/A

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes