Add typed JSON output to theme rename

[gonzaloriestra]

WHY are these changes introduced?

theme rename has no JSON result contract, so automation must parse terminal output.

Closes shop/issues-develop#23692.

WHAT is this pull request doing?

Return status: "success" and originalName alongside the renamed theme, using the shared mutation success schema. Multiple environments carry these fields inside each successful result, with no overall success claim.

Return the renamed API theme as typed data and move final output into a presenter. Reuse the environment collector from the preceding PR, retaining the name prompt, original theme name, and requested name in terminal output. Add --json, expose the domain-owned schema, and refresh the manifest, README, and generated docs.

Normal output includes:

The theme 'Original' (#1) was renamed to 'Renamed Theme'

Matching JSON:

{
  "status": "success",
  "originalName": "Original",
  "theme": {
    "id": 1,
    "name": "Renamed Theme",
    "role": "unpublished",
    "processing": false,
    "createdAtRuntime": false,
    "shop": "example.myshopify.com"
  }
}

The optional src field is retained when present. Multiple environments return {"environments":[{"environment":"staging","result":...}]} in configured order. Failed or invalid environments are omitted and reported on stderr; total failure returns {"environments":[]}. Existing exit behavior and single-environment presentation are preserved.

How to manually test your changes?

pnpm shopify theme rename --help
pnpm shopify theme rename --json-schema
pnpm shopify theme rename --store "$STORE" --theme "$THEME_ID" --name "Renamed Theme"
pnpm shopify theme rename --store "$STORE" --theme "$THEME_ID" --name "Renamed Theme" --json
pnpm shopify theme rename --environment staging --environment production --theme "$THEME_ID" --name "Renamed Theme" --json

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• A single changeset for all theme migrations is added in the last PR, #8682.

[isaacroldan]

I think this schema should include at least status: success (outside of the theme object).
And maybe also the original name?

[gonzaloriestra]

Added top-level status: "success" using the shared mutation schema, plus originalName. The theme object contains the updated name returned by the API. Both fields are also included in each successful environment result.

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/base-command.d.ts

@@ -35,6 +35,7 @@ declare abstract class BaseCommand extends Command {
         argv: string[];
     }>;
     protected environmentsFilename(): string | undefined;
+    protected validateNonTTYFlags(flags: FlagOutput): void;
     protected failMissingNonTTYFlags(flags: FlagOutput, requiredFlags: string[]): void;
     private failMissingNonTTYFlagRequirements;
     private applicableNonTTYFlagRequirements;