Utilize NPM @dapr

Describe the proposal

We have now been granted access to the @dapr organization on NPM.

I propose to start using it under @dapr/dapr instead of dapr-client

Since this is a critical change, I propose on maintaining both in the release pipeline where we in the build.yml process setup an extra step that modifies package.json and swaps the name for @dapr/dapr and releases with the new NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN_DAPR }} env variable

[XavierGeerinck]

I would follow @shubham1172 his idea, allowing people to adopt gradually as NPM packages like to remain on a version.

Personally, I would maintain the dapr-client for around 6 months or until we are able to measure 0 download rate on it

[paulyuk]

Hi there. This sounds like a breaking change. The way I would do that is provide a new version and allow users time to adopt it. I agree with Xavier we should use data/telemetry to measure people moving off of the current version. We need to make this change very clear and visible too IMO.

Now in terms of how to do this best in NPM this will be my first time. I would weigh what Xavier recommends heavily. We can also consult with the experts in VS Code too.