Make boolean environment variables less pedantic

[felddy]

Feature description

Some of the optional environment variables are booleans. While to documentation does say to set them to true to take effect, the implementation could be more lenient.

The implementation of the boolean variable CONTAINER_VERBOSE is a good example of how to handle these types of toggles:

foundryvtt-docker/src/logging.sh

Lines 15 to 17 in 3f4572d

	if [[ "${CONTAINER_VERBOSE:-}" ]]; then
	echo -e "${LOG_NAME} | $(date +%Y-%m-%d\ %H:%M:%S) | [${BLUE}debug${RESET}] $*"
	fi

It probably makes sense to explicitly document that the variable should be unset or empty and not false to disable a function.

Another approach would be to normalize all the expected variables at the start of the entry point.

Motivation

See:

• Server not writing to options.json and CONTAINER_PRESERVE_CONFIG not being respected #581

Example

Instead of setting a boolean environment variable exactly to true, it can be set to any non-empty value.

Compliant variables:

• CONTAINER_VERBOSE

Candidate variables:

• CONTAINER_PRESERVE_CONFIG
• FOUNDRY_IP_DISCOVERY
• FOUNDRY_MINIFY_STATIC_FILES
• FOUNDRY_PROXY_SSL
• FOUNDRY_UPNP

Pitch

To make it easier for users to successfully configure the container.

Code of Conduct

• I agree to follow this project's Code of Conduct