feat: prefix the project name on environment display labels

[nicknisi]

Follow-up to #228.

Why

Teams can hold multiple projects, and environment names are only unique per project — two projects can each have a Staging. Everywhere the CLI prints a bare environment name (profile list, the picker, environment use confirmations), that name is ambiguous exactly when disambiguation matters.

What

Environment labels are now Project > Environment:

    Name        Type      Endpoint   Environment
    staging     Sandbox   default    Nick's Team's Project > test12
▸   staging-3   Sandbox   default    cli-branding-smoke > Staging

• projectName is stored on profiles alongside environmentName, captured by every resolution path (login clientId join, picker, healing, environment use) and healed the same way — existing profiles backfill on the next environment-scoped command with no migration
• Applied to: profile list (table + --json field), the profile switch hint, the environment picker labels, and the environment use confirmation (human + --json)
• environment list is unchanged — it already has a dedicated Project column
• New formatEnvironmentLabel() shared by the TeamEnvironment-shaped call sites

Verification

• 2707 tests passing (3 new), typecheck clean
• Live against a real two-project team: labels render project-prefixed, heal backfilled projectName onto pre-existing profiles, environment use round-trip confirmed

[greptile-apps]

Greptile Summary

The PR disambiguates environment display labels by prefixing environment names with their owning project and persists that project metadata on local profiles.

• Maps each fetched environment to its owning project name.
• Persists and opportunistically heals projectName alongside environment IDs and names.
• Uses project-prefixed labels in profile listings, pickers, switch hints, and environment-use output.
• Adds regression coverage that passes a project-bearing GraphQL response through profile resolution.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
src/lib/environment-target.ts	Correctly maps project ownership onto environments, propagates it through profile resolution and healing, and centralizes project-prefixed labels.
src/lib/environment-target.spec.ts	Adds the requested end-to-end regression coverage proving that a project name from the GraphQL response reaches the stored profile.
src/lib/config-store.ts	Extends persisted environment profiles and no-op write detection to include project names.
src/commands/environment.ts	Persists the selected project name and includes the disambiguated label and structured project field in environment-use output.
src/commands/env.ts	Displays project-prefixed environment labels and exposes the stored project name in JSON profile listings.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    A[Team projects response] --> B[Map environments with owning projectName]
    B --> C[Resolve or select environment]
    C --> D[Persist environmentId, environmentName, and projectName]
    D --> E[Format Project > Environment]
    E --> F[Profile list, switch hint, picker, and use confirmation]

Loading

_{Reviews (3): Last reviewed commit: "test: cover the GraphQL project-name map..." | Re-trigger Greptile}