[FLINK-9156][REST][CLI] Update --jobmanager option logic for REST client

[zentol]

What is the purpose of the change

With this PR the --jobmanager option is properly respected by the RestClusterClient. The problem was that the existing code was only setting JobManagerOptions.ADDRESS and JobManagerOptions.PORT, but not the corresponding RestOptions that are used for all REST API calls. The RestOptions are accessed inHighAvailabilityServicesUtils#createHighAvailabilityServices to create the webmonitor URL that is used by the client.

Brief change log

• set appropriate RestOptions in CliFrontend#setJobManagerAddressInConfig
• add test

Verifying this change

• run RestClusterClientTest#testRESTManualConfigurationOverride

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[GJL]

Some comments of rather cosmetic nature.

[GJL]

There is already a static import for equalTo in this file. I think it should be used, i.e.,

assertThat(webMonitorBaseUrl.getHost(), equalTo(manualHostname));
assertThat(webMonitorBaseUrl.getPort(), equalTo(manualPort));

[GJL]

Maybe configuredHostname, to be consistent with manualHostname. localhost is an arbitrary value, and should not be the name of the variable.

[zentol]

merging.