[enhancement](k8s) Support fqdn mode for fe in k8s enviroment

[yinzhijian]

Proposed changes

Problem summary

大体逻辑沿用#9172

关键改动点：

1. FE的nodename从ip_port_timestamp改为hostname_port_timestamp，如下图中的fe3就是这个实例在k8s中的域名：
   原因：为了避免IP变更后，其它FE实例的IP使用了该IP，比如FE3的原始IP为172.18.0.4，动态变更为172.18.0.50，而后新增了一个FE4，它的IP为172.18.0.4，这时如果还使用ip_port_timestamp形式，则无法直观的从name中区分彼此。
   风险点：可能影响依赖Name解析ip、port的外部程序，无法识别正确的IP。

2. FDQNManager定期便利所有的FE，检查域名对应的IP是否已经改变，如果改变：
   2.1 通过BDBHA的updateAddress方法通知所有peers，保证bdbje层面的一致性。【现在直接以域名作为BDBJE的address，不需要更改IP时再更新】
   2.2 改变master自身内存记录的IP
   2.3 通过editlog同步给其它FE，改变其它follower内存中记录的FE ip信息。

3. Frontend的meta持久化方式改为了json格式，方便后续字段的变更。

4. deploy manger K8s支持IP变更（delete pod后stateful自动加回，ip跟原始的不一致）

Changes:

1. The nodename of FE changes from ip_port_timestamp to hostname_port_timestamp, as shown in the following figure, fe3 is the hostname of this instance in k8s:

Reason: To avoid the scenario that other FE instances use the changed IP after IP change, for example, the original IP of FE3 is 172.18.0.4, changed dynamically to 172.18.0.50, and later a new FE4 is added with IP 172.18.0.4, if the ip_port_timestamp form is still used, the existing program cannot distinguish each other from the name.

Risk: The external program that relies on Name resolution for IP and port recognition may be affected and cannot recognize the correct IP.

2. FDQNManager regularly visits all FEs to check if the IP corresponding to the hostname has changed. If changed:
   2.1 Notify all peers through the updateAddress method of BDBHA to ensure consistency at the bdbje level.
   2.2 Change the IP information recorded in memory by the master itself
   2.3 Synchronize to other FEs through the editlog to change the IP information recorded in memory by other followers.
3. The persistence method of Frontend meta is changed to json format for ease of future field changes.

Checklist(Required)

1. Does it affect the original behavior:
   • Yes
   • No
   • I don't know
2. Has unit tests been added:
   • Yes
   • No
   • No Need
3. Has document been added or modified:
   • Yes
   • No
   • No Need
4. Does it need to update dependencies:
   • Yes
   • No
5. Are there any changes that cannot be rolled back:
   • Yes (If Yes, please explain WHY)
   • No

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[yinzhijian]

run buildall

[hello-stephen]

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.37 seconds
stream load tsv: 471 seconds loaded 74807831229 Bytes, about 151 MB/s
stream load json: 39 seconds loaded 2358488459 Bytes, about 57 MB/s
stream load orc: 74 seconds loaded 1101869774 Bytes, about 14 MB/s
stream load parquet: 32 seconds loaded 861443392 Bytes, about 25 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230304043511_clickbench_pr_108371.html

[yinzhijian]

run buildp0

[yinzhijian]

run buildp0

[yinzhijian]

run p0

[yinzhijian]

run p0

[yinzhijian]

run buildall

[morningman]

LGTM

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.

[yinzhijian]

run buildall

[yinzhijian]

run buildall

[yinzhijian]

run p0

[yinzhijian]

run beut build CheckStyle ClangFormatter LicenseCheck ShellCheck

[yinzhijian]

sh buildall

[morningman]

run buildall

[yinzhijian]

run buildall

[morningman]

run buildall

[morningman]

LGTM