Redis state store component doesn't distinguish between network and Redis errors on Set

[elena-kolevska]

Expected Behavior

When setting a key in Redis errors out, as a developer, I should know the reason. For example if the error is due to an old etag I should retry with a new etag, if it's because Redis is unavailable, I should retry with some kind of retry policy.

Actual Behavior

Dapr returns the same error for both cases mentioned above.

Steps to Reproduce the Problem

Case 1: Try to save a key with an inexistant etag.
Case 2: Start Dapr, stop Redis, try to save a valid key (ex. no etag).

Release Note

RELEASE NOTE:
RELEASE NOTE: FIX Distinguish between Redis and network errors in State API