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

Author: ramanvasi

pkg/devspace/compose/manager.go

@@ -44,6 +44,7 @@ func LoadDockerComposeProject(path string) (*composetypes.Project, error) {
 				Content: composeFile,
 			},
 		},
+		Environment: map[string]string{},
 	})
 	if err != nil {
 		return nil, err

pkg/devspace/compose/testdata/named_project/devspace.yaml

@@ -0,0 +1,9 @@
+version: v2beta1
+name: docker-compose
+deployments:
+  web:
+    helm:
+      values:
+        containers:
+          - name: web-container
+            image: nginx:latest

pkg/devspace/compose/testdata/named_project/docker-compose.yaml

@@ -0,0 +1,4 @@
+name: myproject
+services:
+  web:
+    image: nginx:latest