[Improve][DataProxy] Optimize common.properties related control mechanism

[gosonzhang]

Description

In the current configuration management of DataProxy, there are two parts related to common.properties control implementation, CommonPropertiesHolder and ConfigManager.getCommonProperties(). According to the analysis, this part needs to simplify the two sets of implementations into one set, and at the same time, the relevant implementation logic is adjusted as follows :

1. It is necessary to add a mandatory requirement for common.properties configuration: the configuration file must exist when the node starts, if the file does not exist, the file fails to be read, the file content parsing fails, or the required fields in the file are not configured, the DataProxy node must output the error log, and exits;
2. common.properties is only loaded at startup, and does not need to be loaded during operation;
3. The acquisition of the Manager IP address in common.properties must support multiple strategies, such as configuring the domain name port, configuring the IP and port, or obtaining the corresponding Manager connection address provided by other third-party components;
4. Unify the field configuration tags in common.properties, and align the field configuration tags that are repeated, have the same meaning but misaligned names, and are scattered everywhere

InLong Component

InLong DataProxy

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct