Fix: Use `drasi apply` instead of `kubectl apply` in Dapr + darsi tutorial

[sahajdeepsingh651]

The Dapr + Drasi tutorial instructs users to apply Drasi resources using kubectl apply. However, Drasi resources are not Kubernetes CRDs and must be applied using drasi apply

Following the documented commands results in errors such as:
kubectl apply -f drasi/sources/

resource mapping not found for name: "" namespace: "" from "drasi/sources/customers.yaml": no matches for kind "Source" in version "v1"
ensure CRDs are installed first
resource mapping not found for name: "" namespace: "" from "drasi/sources/orders.yaml": no matches for kind "Source" in version "v1"
ensure CRDs are installed first
resource mapping not found for name: "" namespace: "" from "drasi/sources/products.yaml": no matches for kind "Source" in version "v1"
ensure CRDs are installed first
resource mapping not found for name: "" namespace: "" from "drasi/sources/reviews.yaml": no matches for kind "Source" in version "v1"
ensure CRDs are installed first

[sahajdeepsingh651]

I investigated this issue further and verified that the failure occurs because Drasi resources are not Kubernetes CRDs and therefore cannot be applied using kubectl apply.
Drasi resources (Source, ContinuousQuery, and Reaction) must be deployed via the Drasi API using the drasi CLI.
Proposed Solution

Replace:
kubectl apply -f drasi/dir/
with:
drasi apply -f drasi/dir/*

Changes Made
I have implemented and tested this change locally in the following locations:

• tutorial/dapr/README.md
• scripts/setup-tutorial.sh
• scripts/setup-tutorial.ps1
• .devcontainer/dapr/post-create.sh

After applying these updates, Drasi sources, queries, and reactions deploy successfully and the tutorial services function as expected.

can @amansinghoriginal assign this issue to me ,I have made necessary changes and want to raise a PR for this

[sahajdeepsingh651]

hi @amansinghoriginal ,I have opened a PR regarding this ,would appreciate your review when you get a chance.
thanks