Workflow API to bypass some beta api criteria

[nyemade-uversky]

Allow Workflow API to bypass some beta api criteria

This is a proposal for allowing Dapr Workflow (WF) to reach beta status without having to meet the criteria that is irrelevant to the workflow api specifically API Lifecycle.

Background

Dapr WF differs from other Dapr APIs in that there is only one component implamentation of the API, the built-in actor-based wf engine. Therefore this makes it difficult to meet only the following Beta criteria:

Beta

• E2E tests are up-to-date and comprehensive
• SDK spec is updated
• No major changes to the API have occurred in the last XXX time period (releases? months?)
• Support in core SDKs
  • Python (+ docs/quickstarts)
  • Java Workflow implementation in SDK java-sdk#839
  • .NET (+ docs/quickstarts)
• Workflow Python SDK DTF support enhancements
• Performance tests exist but do not block builds

EDIT (8/17/23):
Go and JS will be supported as part of stable requirements, but not as part of beta

---

Closes #30

[yaron2]

@nyemade-uversky this should be a proposal in the form of a regular proposal, for example #28. You can remove irrelevant sections.

[nyemade-uversky]

@paulyuk and @yaron2 I've updated the PR with content from the issue.