Support loading configuration from both YAML files and env vars

[lippserd]

I will keep the original PR description as a reference, but the implementation now uses config.Load() from our Go libs.

With this PR Icinga DB supports configuration loading in three scenarios:

1. Load configuration solely from YAML files when no relevant environment variables are set.
2. Combine YAML file and environment variable configurations, allowing environment variables to supplement or override possible incomplete YAML configurations.
3. Load entirely from environment variables if the default YAML config file is absent and no specific config path is provided by the user.

config.FromYAMLFile() is still called first but continuation with config.FromEnv() is allowed by handling:

• ErrInvalidConfiguration: The configuration may be incomplete and will be revalidated in config.FromEnv().
• Non-existent file errors: If no explicit config path is set, fallback to environment variables is allowed.

config.FromEnv() is called regardless of the outcome from config.FromYAMLFile(). If no environment variables are set, configuration relies entirely on YAML. Otherwise, environment variables can supplement, override YAML settings, or serve as the sole source. config.FromEnv() also includes validation, ensuring completeness after considering both sources.

Possible alternative implementations:

• If the config path is the default, os.Stat() could be used before calling config.FromYAMLFile(), rather than handling non-existent file errors. This approach would split the logic into two sections and add an additional if block.
• Don't call Validate() in the config package automatically. Instead, require it to be called manually. I appreciate that library-wise, both config.FromYAMLFile() and config.FromEnv() include validation allowing them to be used without needing an additional function call on their own. When combining them, I think it's straightforward to use errors.Is() to check for ErrInvalidConfiguration, i.e. errors from Validate().

requires Icinga/icinga-go-library#87
requires #879

closes #756

[oxzi]

This works as far as I have tested it.

However, the error output may be misleading for a non-existing /etc/icingadb/config.yml file when not explicitly setting the --config flag, relying on the default.

$ stat /etc/icingadb/config.yml
stat: cannot statx '/etc/icingadb/config.yml': No such file or directory

$ ./icingadb
invalid configuration: database host missing
$ ./icingadb -c /etc/icingadb/config.yml
can't open YAML file /etc/icingadb/config.yml: open /etc/icingadb/config.yml: no such file or directory

If there are no ICINGADB_ environment variables and the default config is not existing, the reported error does not state that the expected file does not exist, but says that certain fields are absent. But honestly, I don't know how to address this. For a package installations the config file should be present.

[oxzi]

There is also the config_test.go file, testing against the now unused config.FromYAMLFile function. Maybe you want to remove this test case and create another one for YAML-only, environment-only, and mixed-setups.