Consider the use of Dapr Shared for Dapr in standalone mode

[salaboy]

Dapr Shared allows you to create new standalone Daprd instances without the need for a proxy.
Dapr Shared is distributed as a helm chart so a controller to install the helm chart instead of creating a new dapr-proxy deployment might be the only thing needed.

https://github.com/dapr-sandbox/dapr-shared

I will be more than happy to assist with this work, but I will need to pair up with one of the OpenFunction maintainers to make these changes.

[benjaminhuo]

I will be more than happy to assist with this work, but I will need to pair up with one of the OpenFunction maintainers to make these changes.

@salaboy Thanks for the update, dapr shared looks great.

@wrongerror can help on this enhancement.
Also @wanjunlei can help to review the proposal and changes too.

[salaboy]

@benjaminhuo can you help coordinating? I do see two mayor changes:

1. Upgrading the Dapr version being used (including the Dapr SDK into the openfunctions framework), this will allow us to show workflows and functions together
2. Changing slightly the logic of the controller that deploys Dapr in standalone mode to deploy the Dapr Shared chart.. There are several controllers out there that create Helm Releases so we just need to follow that approach.