fix: populate initProcessEnabled in containerDefinition CreateResource

Extract LinuxParameters.InitProcessEnabled from the AWS SDK container
definition and pass it to the CreateResource call so the field returns
actual data instead of always defaulting to false.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: tas50

providers/aws/resources/aws_ecs.go

@@ -842,6 +842,10 @@ func (a *mqlAwsEcs) createContainerDefinitionResource(taskDefArn string, cd *ecs
 		memory = int64(*cd.Memory)
 	}
 	cpu := int64(cd.Cpu)
+	initProcessEnabled := false
+	if cd.LinuxParameters != nil && cd.LinuxParameters.InitProcessEnabled != nil {
+		initProcessEnabled = *cd.LinuxParameters.InitProcessEnabled
+	}
 
 	// Create environment variables
 	envVars := []any{}
@@ -974,6 +978,7 @@ func (a *mqlAwsEcs) createContainerDefinitionResource(taskDefArn string, cd *ecs
 			"memory":                 llx.IntData(memory),
 			"cpu":                    llx.IntData(cpu),
 			"portMappings":           llx.ArrayData(portMappings, types.Resource("aws.ecs.taskDefinition.containerDefinition.portMapping")),
+			"initProcessEnabled":     llx.BoolData(initProcessEnabled),
 		})
 }