docs: fix activation page

Author: FabianKramm

docs/pages/configuration/profiles/activation.mdx

@@ -9,8 +9,8 @@ The `activation` option is optional and allows you to activate a profile using r
 #### Example: Defining a Profile Activation using `vars`
 ```yaml {1-3,7-8}
 vars:
-- name: ENV
-  default: development
+  ENV:
+    default: development
 profiles:
 - name: production
   activation:
@@ -92,24 +92,20 @@ When `dependencies` are referenced from a `devspace.yaml`, the dependency's prof
 
 ```yaml
 dependencies:
-- name: component-1
-  source:
+  component-1:
     path: ./component-1
-- name: component-2
-  source:
+  component-2:
     path: ./component-2
 ```
 
 #### Example: Disable Activations by Dependency
 The `disableProfileActivation` option can be used to disable profile activations for specific dependencies. In the following example, the activations for `./component-1/devspace.yaml` would be ignored, while the activations in `./component-2/devspace.yaml` would be evaluated:
 ```yaml {5}
 dependencies:
-- name: component-1
-  source:
+  component-1:
     path: ./component-1
-  disableProfileActivation: true
-- name: component-2
-  source:
+    disableProfileActivation: true
+  component-2:
     path: ./component-2
 ```