[flagd] Support custom schemes (name resolvers)

[toddbaert]

As described here, we wish to support custom name revolvers for additional control and configuration according to user's infrastructure. In order to make use of this, we must support the creation of channels created with NettyChannelBuilder.forTarget, and expose an option in the flagd that use a "target string" instead of a host/port combination.

Requirements:

• optional usage of channel built using .forTarget (see:

  java-sdk-contrib/providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/resolver/common/ChannelBuilder.java

  Line 30 in 4197d32

  public static ManagedChannel nettyChannel(final FlagdOptions options) {

  )
• changes in options to allow specifying a target string
  • support env-var based configuration as well, as with existing options
  • consistent with [flagd] Support custom schemes (name resolvers) go-sdk-contrib#585
• no breaking changes
• associated unit tests (e2e not necessary)

cc @pradeepbbl

[pradeepbbl]

sounds good to me and I'm happy to work on it

[toddbaert]

sounds good to me and I'm happy to work on it

assigned!