realtime segment completion is broken with HTTPS

If a controller is configured with HTTPS ingress ONLY, segment upload fails due to a lack of protocol information pass-thru in the segment uploader. A typical exception looks like this:

`12:59:37.439 ERROR [ServerSegmentCompletionProtocolHandler] [mytable__0__0__20210602T1951Z] Could not send request http://localhost:18998/segmentConsumed?reason=rowLimit&streamPartitionMsgOffset=2500&instance=Server_localhost_8098&offset=-1&name=mytable__0__0__20210602T1951Z&rowCount=2500
org.apache.http.NoHttpResponseException: localhost:18998 failed to respond`

Solution: either pass protocol via zookeeper or add a configuration option to pin the segment uploader's connection scheme.