fix: prevent nil map panic when docker-compose.yaml has top-level name field

When a docker-compose.yaml includes a top-level 'name:' field, the
compose-go loader attempts to assign to ConfigDetails.Environment which
is nil, causing a panic.

Initialize the Environment map to an empty map before calling the loader.

Fixes #2970