Support DAPR_HTTP_ENDPOINT and/or DAPR_GRPC_ENDPOINT

[artursouza]

Describe the proposal

Allow consistent way to configure endpoint for Dapr's sidecar, while enabling remote sidecar configuration.

Child of dapr/dapr#6035

SDK should parse these in a consistent way, so operators have a consistent environment variable to set for Dapr apps. Right now, each SDK has their own way of configuring the endpoint for Dapr's sidecar.

If SDK allows gRPC communication from SDK to sidecar, then DAPR_GRPC_ENDPOINT must be supported.
If SDK allows HTTP communication from SDK to sidecar, then DAPR_HTTP_ENDPOINT must be supported.
DAPR_HTTP_ENDPOINT and DAPR_GRPC_ENDPOINT and not exclusive, meaning it is acceptable to support both, like in the Java SDK, if the SDK supports both protocols.
Also, companies might decide to offer different endpoints per protocol, so there is not an unique environment variable for both.

[yanleiwang]

I'm new here, and I'd like to know if this issue has been resolved by https://github.com/dapr/go-sdk/pull/475
If not, can you tell me roughly what I need to do, and please assign this task to me