Add aborting workflow execution phase

[katrogan]

Signed-off-by: Katrina Rogan [email protected]

TL;DR

The call to abort a workflow execution results in a two stage process

1. Flyteadmin deletes the workflow CRD and saves the user-provided abort cause (but not phase) in the db
2. Flytepropeller detects the workflow CRD has been deleted and sends and abort event, at which point the execution phase is changed

This is confusing for end users when a delay occurs between (1) and (2). Introducing 'ABORTING' allows us to update the execution phase immediately when handling an abort call, providing a better user experience

Type

• Bug Fix
• Feature
• Plugin

Are all requirements met?

• Code completed
• Smoke tested
• Unit tests added
• Code documentation added
• Any pending items have an associated Issue

Complete description

How did you fix the bug, make the feature etc. Link to any design docs etc

Tracking Issue

flyteorg/flyte#1978

Follow-up issue

NA