[FEATURE REQUEST] Improve Dapr HTTP client error handling

[passuied]

Describe the feature

The error handling experience when calling invoking a method over HTTP is very lacking.
There are many cases where the exception thrown is just DaprInternalError with message Dapr Internal Error (UNKNOWN).
It doesn't provide the status code or the reason which are available in the response.

This change intends to address the issue so that:

• message is either:
  • the value for the JSON serialized message property returned in the response body if available
  • HTTP status code: {status_code}
• errorCode is either:
  • the value for the JSON serialized errorCode` property returned in the response body if available
  • ERR_DOES_NOT_EXIST if the status_code is 404 and no response body is returned (existing behavior)
  • UNKNOWN otherwise
• status_code is the status code return by the response
• reason is the reason associated to the status code (set by requests library)

Release Note

RELEASE NOTE: ADDImprove Dapr HTTP client error handling