Review the use of configuration parsing utilities in the code

In the CTA code several utility functions are spread across the code and used for parsing different configuration files:

• frontend/common/Config.cpp
• common/Configuration.cpp
• cmtline/standalone_cli_tools (XrdSsiPb::Config)
• ... ?

Would it be worth to review our approach to get config information ?

PS: This was motivated by attempt to pass frontend Config object to OStoreDB and running into linker problems (out of the box) since OStoreDB was missing access to the frontend specific Config.cpp implementation:

/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: ../scheduler/libctascheduler.so.0.1.0: undefined reference to `cta::frontend::Config::getOptionValueInt(std::string const&) const'