Dapr namespace different to defined namespace

[derchirurg]

🔥 Bug Description

If developing a dapr solution, it is currently not possible to deploy the application and the dapr dependencies in the same namespace.
The Dapr dependencies are always deployed to the namespace "dapr-system". This is caused by dapr init -k.
Maybe it would be great to deploy the dapr components to the same namespace as defined in the aspirate manifest.
e.g. dapr init -k -n <namespace>

🔍 Steps to Reproduce the Bug

Generate and apply dapr application.

🧯 Possible Solution

Use dapr init -k -n <namespace> in src/Aspirate.Services/Implementations/DaprCliService.cs