During workflow/actor registration, validate metadata endpoint reflects actor-compatible state store

## Describe the feature
A recurring concern was raised [in Discord](https://discord.com/channels/778680217417809931/778693130303832135/1296455192962928711) and then in https://github.com/dapr/dapr/issues/8208 indicating that it was unclear why the app would fail to start up during workflow initialization and this was later traced to there not being an actorStateStore registered to use.

While this makes for a prime documentation target to clarify, the SDK could do more on this front as well.

The specific details need more consideration, but I'm initially thinking that because of the [hot reload capability for components](https://docs.dapr.io/operations/components/component-updates/), this should be implemented as a sort of health check (read: recurring) registered whenever the developer registers the Dapr actor runtime or the Dapr workflow client. As @olitomlinson [mentioned](https://github.com/dapr/dapr/issues/8208#issuecomment-2420068982), rather than necessarily expand on the Health API here, this could simply retrieve the configuration from the Metadata endpoint and indicate whether an actor-compatible state store is registered, then fail in the application with a clear exception.

## Release Note

RELEASE NOTE: **ADD** Validate whether actor state store is correctly registered during SDK initialization preempting endless connection failures