Give every Postman environment a consistent name

**Objective:** Make environment names consistent, using `{naming-convention}` as the target pattern (default: Title Case stage names Development, Testing, Staging, Production, with any product prefix kept, e.g. Payments - Staging).

**Step 1: Load environments**

Call `postman-get-environments`. Keep environment-id, environment-uid, name, owner, public and updated-at.

**Step 2: Find inconsistencies**

* Stage synonyms: dev/develop/development, test/qa/testing, stage/stg/staging, prod/prd/live/production.
* Mixed case, stray spaces, trailing copy markers such as Copy, (1) or - old.
* Duplicates: two environments that normalize to the same name. Do not rename these into a collision; flag them instead, and use `postman-get-environment-variables` with `environment-id` to say whether their variable keys match (likely a duplicate) or not.
* Check monitors with `postman-get-monitors` and note which environments are used by a monitor, so the user knows what a rename touches. Monitors refer to the environment by UID, so they keep working after a rename.

**Step 3: Propose**

A numbered table: current name, proposed name, owner, used by monitors (yes/no), reason.

**Step 4: Apply what is approved**

Ask which numbered items to apply. For each approved item, call `postman-update-environment` once with `environment-uid` and the new `name`, and report the result.

**Rules & Guidelines:**

* Rename only what the user picks by number. Never rename into a name that already exists.
* `postman-update-environment` is the only write. Do NOT call `postman-add-environment` or any other write tool.
* Leave environments owned by other people flagged rather than renamed unless the user confirms.

**Validation:**

* If every name already follows the convention, say so and make no write calls.