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

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.