[Workflow] Improve management API usability

[cgillum]

Description

This PR contains breaking changes to the v1.10 workflow management client APIs. The point of these changes is to improve the usability of these core APIs. This includes adding a few additional convenience types and methods.

This PR also updates the console app sample, replacing the DaprWorkflowClient with DaprClient, which was always the intent.

Issue reference

Resolves #1027.

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

FYI @RyanLettieri

[codecov]

Codecov Report

Merging #1087 (5c55396) into master (610632a) will decrease coverage by 0.57%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1087      +/-   ##
==========================================
- Coverage   68.07%   67.51%   -0.57%     
==========================================
  Files         169      170       +1     
  Lines        5604     5652      +48     
  Branches      592      600       +8     
==========================================
+ Hits         3815     3816       +1     
- Misses       1649     1696      +47     
  Partials      140      140              

Flag	Coverage Δ
net6	67.42% <0.00%> (-0.58%)	⬇️
net7	67.42% <0.00%> (-0.58%)	⬇️
netcoreapp3.1	67.48% <0.00%> (-0.57%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/Dapr.Client/DaprClient.cs	73.52% <0.00%> (-19.07%)	⬇️
src/Dapr.Client/DaprClientGrpc.cs	74.17% <0.00%> (-0.95%)	⬇️
src/Dapr.Client/GetWorkflowResponse.cs	0.00% <0.00%> (ø)
src/Dapr.Client/WorkflowFailureDetails.cs	0.00% <0.00%> (ø)

[RyanLettieri]

While you didn't touch the file, we should update the asserts inside WorkflowTest.cs to use the enumeration: "WorkflowRuntimeStatus" for the status of the runtime rather than hardcoded values such as "RUNNING", "SUSPENDED", etc.

[cgillum]

While you didn't touch the file, we should update the asserts inside WorkflowTest.cs to use the enumeration: "WorkflowRuntimeStatus" for the status of the runtime rather than hardcoded values such as "RUNNING", "SUSPENDED", etc.

Oh, interesting. I've never used FluentAssertions before, but it seems like a weakness in its design. Ideally the compiler would have caught this. I'll go ahead and fix that, along with your other suggestions.

[halspang]

Mostly nitpicks, overall seems fine.