Updating Readme's to default to dapr run -f .

[paulyuk]

Description

Change readme's to favor and default to multi-app-run behavior using dapr run -f .

Carefully tweak test with 15 second sleep and up to 60second timeout for predictable automated testing.

Checklist

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

• The quickstart code compiles correctly
• You've tested new builds of the quickstart if you changed quickstart code
• You've updated the quickstart's README if necessary
• If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

[msfussell]

I would not remove the steps to show how to start these individually, just put these after the multi-app run. Showing how to use the dapr run command for a single app is still important IMO (the parameters) and needed until the multi-app run command becomes more adopted. If in time multi-app run shows its value, then we can consider having just that, but too early now IMO.

[paulyuk]

I would not remove the steps to show how to start these individually, just put these after the multi-app run. Showing how to use the dapr run command for a single app is still important IMO (the parameters) and needed until the multi-app run command becomes more adopted. If in time multi-app run shows its value, then we can consider having just that, but too early now IMO.

Ok sounds like a reasonable compromise. I'm not a super big fan of lots of options which themselves create more conceptual overhead, but given where we are, I agree this is a good way to ease into the new model and ensure it's ready or not to be the main thing we show and do.

[philliphoff]

I might also note in the READMEs that dapr run -f on Windows requires the upcoming Dapr 1.12.

[msfussell]

LGTM

[msfussell]

Approved