Suggestions: Update PalWorldSettings.ini defaults and make them truly default

[Araeos]

Hi, with the release of 1.0.0 I tried checking if the default world settings have changed by removing most settings from the palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini file and ensuring that it does not get overriden by setting DISABLE_GENERATE_SETTINGS=true I observed the resulting settings via sudo docker exec -it palworld-server rest-cli settings > palworld-server-v1.0.0-defaults.settings and compared them to the defaults the docker container generated with DISABLE_GENERATE_SETTINGS=false.
The result can be seen in this screenshot

Obivously the PalEggDefaultHatchingTime of 72 real-time hours is a bug in the defaults choosen by the docker container, but that got me thinking: The palworld server does choose defaults when they are not specified in the PalWorldSettings.ini file. So wouldn't it make sense for the container to set only a specific value when the corresponding environment variable is not empty, such that all settings that are not specifically choosen will get their defaults from the palworld server binary and not forcibly set via the PalWorldSettings.ini.template?

[thijsvanloef]

Already created a PR #867