Starting Draupnir with --draupnir-config incorrectly warns that he config can't be found because of theConfig package behaviour

[Gnuxie]

We always try to load Config even when the --draupnir-config argument is provided, and that causes this error message. Which is confusing to anyone debugging issues with the config file.

[Gnuxie]

yarn test:manual                                                            ✔ 
Debugger attached.
yarn run v1.22.22
$ ts-node test/integration/manualLaunchScript.ts --draupnir-config config/harness.yaml
Debugger attached.
Wed, 09 Oct 2024 11:00:07 GMT [INFO] [Draupnir config] Configuration meta: {
  "configPath": "config/harness.yaml",
  "isDraupnirConfigOptionUsed": true,
  "isAccessTokenPathOptionUsed": false,
  "isPasswordPathOptionUsed": false
}

Can't reproduce, but that might be because config/default.yaml exists? not sure

[Gnuxie]

ok i got it

WARNING: No configurations found in configuration directory:/home/user/experiments/Draupnir/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.

[Gnuxie]

Now to mangle this, sigh this is shit https://github.com/node-config/node-config/blob/8681019099f43eb4762d5cecf2f42ab9e99f3f5e/lib/config.js#L1520-L1522 . Hmm, so we'd have to mangle the environment variables before we import Config and then make our own version of the warning when draupnir config isn't present.... oh mare.