[Reporting] Regression bug with xpack.reporting.capture.browser.chromium.proxy.bypass

[tsullivan]

Kibana version: 7.8.0

Describe the bug:
A bug introduced in regards to the following setting: xpack.reporting.capture.browser.chromium.proxy.bypass

FATAL Error: [config validation of [xpack.reporting].capture.browser.chromium.proxy.bypass.3]: value must be a valid hostname (see RFC 1123).

According to the documentation : https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html , it is valid to contain wildcards and port numbers: *.elastic.co", ".elastic.co", ".elastic.co:5601.

Also port numbers in names in the array doesn't seem to be allowed , even though the documentation says it is valid.

Additional information:
The bypass setting can be upgraded by using an array of host names, instead of a wildcard. Example:

xpack.reporting.capture.browser.chromium.proxy.enabled : true
xpack.reporting.capture.browser.chromium.proxy.server: http://example.com:8080
xpack.reporting.capture.browser.chromium.proxy.bypass : [ "foo.example.com", "bar.example.com", "bats.example.com" ]

whereas in 7.7.x, this config could have been used:

xpack.reporting.capture.browser.chromium.proxy.enabled : true
xpack.reporting.capture.browser.chromium.proxy.server: http://example:8080
xpack.reporting.capture.browser.chromium.proxy.bypass : [ "*.example.com" ]

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[tsullivan]

It looks like the bug was added in this PR, on this line: https://github.com/elastic/kibana/pull/61696/files#diff-e4c9f182be24f47d092c8c3d21878cb5R100