[BUG] flagd v0.5.0 does not work with flagd-proxy provider

[odubajDT]

Observed behavior

./bin/flagd start --sources '[{"uri":"grpc://flagd-proxy-svc.open-feature-operator-system.svc.cluster.local:8015","provider":"grpc","selector":"core.openfeature.dev/test/end-to-end-test"}]'

	 ______   __       ________   _______    ______      
	/_____/\ /_/\     /_______/\ /______/\  /_____/\     
	\::::_\/_\:\ \    \::: _  \ \\::::__\/__\:::_ \ \    
	 \:\/___/\\:\ \    \::(_)  \ \\:\ /____/\\:\ \ \ \   
	  \:::._\/ \:\ \____\:: __  \ \\:\\_  _\/ \:\ \ \ \  
	   \:\ \    \:\/___/\\:.\ \  \ \\:\_\ \ \  \:\/.:| | 
	    \_\/     \_____\/ \__\/\__\/ \_____\/   \____/_/ 														

2023-04-07T12:35:23.011+0200 info cmd/start.go:105 flagd version: dev (898a820), built at: 2023-04-07T12:34:22Z {"component": "start"}
2023-04-07T12:35:23.011+0200 info flag-evaluation/connect_service.go:140 metrics and probes listening at 8014 {"component": "service"}
2023-04-07T12:35:23.011+0200 info flag-evaluation/connect_service.go:50 Flag Evaluation listening at [::]:8013 {"component": "service"}
2023-04-07T12:35:23.011+0200 fatal cmd/start.go:156 rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: address grpc://flagd-proxy-svc.open-feature-operator-system.svc.cluster.local:8015: too many colons in address" {"component": "start"}
github.com/open-feature/flagd/flagd/cmd.glob..func1
/home/odubaj/OpenFeature/flagd/flagd/cmd/start.go:156
github.com/spf13/cobra.(*Command).execute
/home/odubaj/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920
github.com/spf13/cobra.(*Command).ExecuteC
/home/odubaj/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044
github.com/spf13/cobra.(*Command).Execute
/home/odubaj/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
github.com/open-feature/flagd/flagd/cmd.Execute
/home/odubaj/OpenFeature/flagd/flagd/cmd/root.go:37
main.main
/home/odubaj/OpenFeature/flagd/flagd/main.go:30
runtime.main
/usr/local/go/src/runtime/proc.go:250

Expected Behavior

No error

Steps to reproduce

This problem is already fixed in main branch with this commit 0223c23

Therefore it would be nice to release a new bugfix version v0.5.1.

Note: flagd v0.4.5 is not affected