Adds DAPR_GRPC_ENPOINT support to client

[JoshVanL]

PR adds DAPR_GRPC_ENPOINT environment variable support to client.

Address parser respects http[s] schemes, and TLS query options, as per 0008-S-sidecar-endpoint-tls.md.

DAPR_GRPC_ENDPONT takes precedence over DAPR_GRPC_PORT.

[codecov]

Codecov Report

Attention: 28 lines in your changes are missing coverage. Please review.

Comparison is base (ae8becf) 68.96% compared to head (d5e92fc) 69.71%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #475      +/-   ##
==========================================
+ Coverage   68.96%   69.71%   +0.74%     
==========================================
  Files          34       35       +1     
  Lines        2707     2843     +136     
==========================================
+ Hits         1867     1982     +115     
- Misses        732      746      +14     
- Partials      108      115       +7     

Files	Coverage Δ
client/internal/parse.go	92.37% <92.37%> (ø)
client/client.go	65.46% <34.48%> (-4.79%)	⬇️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mikeee]

Are the grpc and grpcs schemas intentional? (They're not parsed)

[JoshVanL]

@mikeee cpuld you elaborate?
The schema should be (hopefully!) following https://github.com/dapr/proposals/blob/main/0008-S-sidecar-endpoint-tls.md

[mikeee]

In the parser lines 168-169 the grpc/s schemas are permitted yet not parsed as there is no handling for those schemas e.g. grpcs://localhost:443 would result in no target. (I understand this is not what the proposal includes - reading this I would be slightly confused if not for the switch statement not explicitly catching tbe rest of the valid schemas)

[mikeee]

Although known, these weren't specified by the proposal and aren't handled in this function otherwise. Should they still be included?

[JoshVanL]

Thanks @mikeee, indeed these should be removed.