[FEATURE] Add optional time delay to no-op step

[dbwiddis]

Is your feature request related to a problem?

Some actions taken by workflow steps take time to propagate to other nodes. In particular, undeploying models do not have immediate effect, and the deprovision workflow includes a short time delay between steps, and an even longer time delay before retrying.

The no-op step exists in part to allow synchronization of multiple previous steps. It can also be used to force a brief time delay between steps.

What solution would you like?

Add an optional time delay (defaulting to 0) to the no-op step. It'll still do nothing, but it'll wait a specified time before doing nothing.

What alternatives have you considered?

Creating a new step with a delay type, that also does nothing.

Do you have any additional context?

OpenSearch has eventual read consistency, typically within 1 second. However, serverless applications may have an even longer delay due to the distributed implementation.