`dfhack-config` should probably follow the portable mode setting

[ab9rf]

we currently store dfhack-config in the DF install folder, but with the new "portable mode" functionality most DF preferences are stored by default in a user profile folder, and we should probably move our user config similarly

notably Core::getScriptPaths has a hardcoded reference which will need to be changed

we probably also need to watch for the portable mode flag to change and react appropriately if it does

[eroen]

This would be great! If the read-only game files and mutable data could be separated, it would be possible to package dfhack for linux distros with minimal hackery.

Currently, apart from the dfhack-config directory, dfhack also creates stdout.log and stderr.log in the game root directory.

As of v52.02, DF itself still attempts to create gamelog.txt and errorlog.txt in the game root directory. If the game directory isn't writable they just don't get created, errors seem to be silently ignored. This should probably be addressed upstream, but perhaps dfhack could override the paths in the meantime?

[ab9rf]

we can't change DF's file system behavior easily