Uncaught ACTOR_NOT_ACTIVATED error emitted from ActorManager.deactivateActor (triggered by automatic cleanup?)

## Expected Behavior

No error to be thrown if the ActorManager cannot deactivate an unactivated actor as part of whatever background work it does by default.

## Actual Behavior

Occasionally an error message in the form of `{"error":"ACTOR_NOT_ACTIVATED","errorMsg":"The actor 3010219526 was not activated"}` is thrown by the Dapr JS SDK and caught by our error tracking services. We do not deactivate actors ourselves, so this must be in accordance with some kind of automatic management on the Dapr SDK's part.

The stacktrace is as follows (actor id = , = our project directory):

```
Error: {"error":"ACTOR_NOT_ACTIVATED","errorMsg":"The actor was not activated"}
ActorManager.deactivateActor(/opt//node_modules/@dapr/dapr/actors/runtime/ActorManager.js:60)
ActorRuntime.deactivate(/opt//node_modules/@dapr/dapr/actors/runtime/ActorRuntime.js:124)
HTTPServerActor.handlerDeactivate(/opt//node_modules/@dapr/dapr/implementation/Server/HTTPServer/actor.js:70)
(/opt//node_modules/dd-trace/packages/datadog-instrumentations/src/router.js:50)
bound handlerDeactivate(/opt//node_modules/dd-trace/packages/datadog-shimmer/src/shimmer.js:26)
Layer.handle [as handle_request](/opt//node_modules/express/lib/router/layer.js:95)
next(/opt//node_modules/express/lib/router/route.js:144)
Route.dispatch(/opt//node_modules/express/lib/router/route.js:114)
(/opt//node_modules/dd-trace/packages/datadog-instrumentations/src/router.js:50)
bound dispatch(/opt//node_modules/dd-trace/packages/datadog-shimmer/src/shimmer.js:26)
Layer.handle [as handle_request](/opt//node_modules/express/lib/router/layer.js:95)
(/opt//node_modules/express/lib/router/index.js:284)
param(/opt//node_modules/express/lib/router/index.js:365)
param(/opt//node_modules/express/lib/router/index.js:376)
param(/opt//node_modules/express/lib/router/index.js:376)
Function.process_params(/opt//node_modules/express/lib/router/index.js:421)
```

## Steps to Reproduce the Problem

Unsure. We are currently evaluating Dapr in our development environment which is low traffic, so presumably we are triggering some kind of idle timeout. The last known activity these actors have before seeing this error is thrown is approximately ~1hr prior. No errors from our code are thrown inside these actors AFAIK.