Add Applications.Dapr/configurationStores local-dev recipe

[SoTrx]

Hey,

This PR introduces a local-dev recipe for Applications.Dapr/configurationStores

It is related to:

• Add Application.Dapr/ConfigurationStores related docs docs#1235
• Implementation of Dapr Building Block: Configuration Store radius#7889

The prerequisite for this PR is Radius pull request, which has now been merged. A new type, Application.Dapr/configurationStores, was introduced in the radius repo and will be recognized by the test workflow running against current PR in the recipes repo.

[Reshrahim]

@SoTrx - Thanks for the contribution. The new recipe should be added to the readme - https://github.com/radius-project/recipes/blob/main/local-dev/README.md

[kachawla]

Thanks @SoTrx. This is great!

@willtsai, @Reshrahim - General question, not directly impacted by this or blocking for this PR but wanted to bring this up now since it adds another dapr recipe. Do we want to organize dapr recipes under a subdirectory or rename the files to be more explicit? I wonder if configurationstore.bicep, statestore.bicep can be confusing without looking at the code.

[Reshrahim]

Thanks @SoTrx. This is great!

@willtsai, @Reshrahim - General question, not directly impacted by this or blocking for this PR but wanted to bring this up now since it adds another dapr recipe. Do we want to organize dapr recipes under a subdirectory or rename the files to be more explicit? I wonder if configurationstore.bicep, statestore.bicep can be confusing without looking at the code.

I guess we can include the prefix dapr to the naming convention to avoid confusion e.g.daprconfigurationstore.bicep. When we enable UDT's, I expect us to do some changes on the directory structure across the board.