Migrage the console server's specifying logic into transport-common

[jasonjoo2010]

Describe what this PR does / why we need it

Because there are similar implementation in both simple-http and netty-http submodules on processing console server's address so migrate it into transport-common.

Does this pull request fix one issue?

NO

Special notes for reviews

Should actually run for verifying.

[codecov-io]

Codecov Report

Merging #926 into master will decrease coverage by 0.45%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #926      +/-   ##
============================================
- Coverage     43.03%   42.58%   -0.46%     
+ Complexity     1568     1444     -124     
============================================
  Files           337      310      -27     
  Lines          9877     8993     -884     
  Branches       1332     1222     -110     
============================================
- Hits           4251     3830     -421     
+ Misses         5097     4696     -401     
+ Partials        529      467      -62

Impacted Files	Coverage Δ	Complexity Δ
...sp/sentinel/slots/system/SystemBlockException.java	0% <0%> (-44.45%)	0% <0%> (-2%)
...a/csp/sentinel/slots/system/SystemRuleManager.java	43.16% <0%> (-21.84%)	7% <0%> (-12%)
.../alibaba/csp/sentinel/slots/system/SystemRule.java	28.57% <0%> (-16.33%)	8% <0%> (-4%)
...libaba/csp/sentinel/slotchain/ResourceWrapper.java	71.42% <0%> (-15.24%)	3% <0%> (-3%)
...m/alibaba/csp/sentinel/node/metric/MetricNode.java	51.94% <0%> (-13.32%)	18% <0%> (-5%)
...aba/csp/sentinel/adapter/servlet/CommonFilter.java	75% <0%> (-12.81%)	10% <0%> (-1%)
...inel/adapter/gateway/sc/SentinelGatewayFilter.java	26.92% <0%> (-8.57%)	3% <0%> (-1%)
.../java/com/alibaba/csp/sentinel/util/SpiLoader.java	8.64% <0%> (-7.69%)	2% <0%> (-2%)
...nel/adapter/reactor/SentinelReactorSubscriber.java	80% <0%> (-6.89%)	19% <0%> (-2%)
...baba/csp/sentinel/slotchain/SlotChainProvider.java	63.15% <0%> (-6.85%)	5% <0%> (+2%)
... and 66 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 20ad3c8...eb9b861. Read the comment docs.

[sczyh30]

Maybe here we could just ignore the invalid item, rather than fail directly. What do you think of it?

[jasonjoo2010]

The dealing in old logics,
it will be just ignored in simple-http while in netty-http an exception is generated (in InetSocketAddress.checkPort()) but also caught immediately in place, log a warning in record.log, print a stack trace to standard output.

Because the logging of sentinel can not be merged into the biz project's logging so the warning may be ignored. So the malformed :port is more like to be eaten and initializing flow will go on without the correct dashboard target.
That's why some guys suffer from no heartbeat / no application registered.

I like the idea of stopping to fix rather than ignore but logging.
But I will also feel ok on keeping the logic the same as how it acted in netty-http.

[sczyh30]

It's okay for me. I'll review the PR these days.

[sczyh30]

Could you please resolve the conflicts?

[jasonjoo2010]

Could you please resolve the conflicts?

They have been resolved.

[sczyh30]

LGTM

[sczyh30]

Thanks!