fix: resolve target-based AB test target name mismatch

The resolveTargetName() function had a false-positive in its startsWith
check that prevented it from applying the project prefix. When the
runtime name equals the project name (the default case), target names
like "Foo-prod" already start with "Foo-" so the guard incorrectly
assumed they were already prefixed and returned them unchanged.

However, post-deploy-http-gateways.ts unconditionally creates targets
as `${projectName}-${tgt.name}` (e.g., "Foo-Foo-prod"), so the AB test
referenced a non-existent target and stayed in NOT_STARTED forever.

The fix removes the startsWith heuristic and always applies the prefix,
matching what post-deploy-http-gateways.ts does.

Author: notgitika

src/cli/operations/deploy/post-deploy-ab-tests.ts

@@ -476,14 +476,11 @@ function resolveConfigBundleVersion(
 }
 
 /**
- * Resolve a variant target name, applying the project prefix if not already present.
- * This handles legacy configs that were created before the prefix requirement.
+ * Resolve a variant target name by applying the project prefix unconditionally.
+ * post-deploy-http-gateways.ts always creates targets as `${projectName}-${tgt.name}`,
+ * so the AB test must reference the same prefixed name.
  */
 function resolveTargetName(targetName: string, projectName: string): string {
-  // If the target name already starts with the project prefix, use as-is to avoid double-prefixing
-  if (targetName.startsWith(`${projectName}-`)) {
-    return targetName;
-  }
   return `${projectName}-${targetName}`;
 }