Don't set both configuration.image and image

Previously we did this to accommodate cloudchamber apply,
but now we just make this change in the apply function.
Otherwise the generated config will have both fields set
which will error when we re-read it.

Author: emily-shen

packages/wrangler/src/__tests__/cloudchamber/apply.test.ts

@@ -1,4 +1,3 @@
-import { writeFileSync } from "node:fs";
 import {
 	getCloudflareContainerRegistry,
 	SchedulingPolicy,

packages/wrangler/src/__tests__/config/configuration.test.ts

@@ -2408,12 +2408,8 @@ describe("normalizeAndValidateConfig()", () => {
 				expect(diagnostics.hasErrors()).toBe(false);
 				expect(config.containers).toEqual([
 					{
-						configuration: {
-							image: "docker.io/something:hello",
-						},
 						class_name: "test-class",
 						name: "test-worker-name-test-class",
-						// this has been set twice to accomodate both cloudchamber and containers
 						image: "docker.io/something:hello",
 						image_build_context: undefined,
 					},

packages/wrangler/src/cloudchamber/apply.ts

@@ -333,6 +333,8 @@ export async function apply(
 	log(dim("Container application changes\n"));
 
 	for (const appConfigNoDefaults of config.containers) {
+		appConfigNoDefaults.configuration ??= {};
+		appConfigNoDefaults.configuration.image = appConfigNoDefaults.image;
 		const application =
 			applicationByNames[
 				appConfigNoDefaults.name ??

packages/wrangler/src/config/validation.ts

@@ -2486,8 +2486,6 @@ function validateContainerApp(
 			}
 			containerAppOptional.image = resolvedImage;
 			containerAppOptional.image_build_context = resolvedBuildContextPath;
-			containerAppOptional.configuration ??= {};
-			containerAppOptional.configuration.image = resolvedImage;
 
 			// Validate rollout related configs
 			if (