[REQUEST] Support "config.nut"-like file in root data folder

[Darxo]

Is your feature request related to a problem? Please describe.

Adding semi-permanent simple debugging changes (for modder) or customization changes (for user) is often complicated and non-standardized.
A modder would need to create a new [dummy] mod for those or temporarily add them to a mod of theirs.
A user would need someone to create a mod for them, somehow create one themselves, or take an existing mod and write around in its zipped .nut files

Describe the solution you'd like

Define a generic name like config.nut and always try to import that file during a late bucket or after hooks.
It is optional, and if it exists it must be at root level, aka in parallel to your mod .zip files inside the data folder
The include would look something like this:

try {
  ::include("config.nut");
}
catch (_e) {} // Do nothing, because this file is optional

Once this is implemented in code, any modder and user can now go ahead and create a config.nut file in their data folder and fill it with many simple changes.
Most notably those can be changes to Const values. Be it making the game easier/harder or quickly toggling non-exposed debugging options. Those changes are easier done and more permanent than if you used the dev console for them.

[Darxo]

I did some testing and arrived at the following setup:

We define that the file must be called _config.nut and that it must be situated at the root level in the data folder (next to all the mods). The name config is already used by a file in the documents folder. The underscore is meant to make it sort to the top of the folder from a user-pov

Then we first confirm that the file is present at all by calling ::IO.enumerateFiles("."), which only spews out the files in the data folder, in the game folder and in the Documents\Battle Brothers (all thrown together). This is still significantly faster than calling ::IO.enumerateFiles("") (takes around 4 seconds to execute)
Unfortunately a simple syntax in _config.nut does not trigger an exception, so we can't apply custom handling in such a case. Instead a regular script error is printed to the log, which points to the line in question.

local isConfigPresent = function()
{
	foreach (fullPath in ::IO.enumerateFiles("."))
	{
		if (fullPath == "./_config")
		{
			return true;
		}
	}
	return false;
}

if (isConfigPresent())
{
	::logInfo("_config.nut was found and will be loaded now");
	try {
		::include("_config.nut");
	}
	catch (_e)
	{
		::logError("_config.nut threw an exception while trying to load");
		::MSU.Log.printData(_e, 2);
	}
	::logInfo("_config.nut loading finished");
}