docs(deployment): name the environment as what os environments bind --build updates (#12480)

`content/docs/deployment/cli.mdx:1532` still read "before updating the
project" — the one site on the page the v5.0 `project` -> `environment`
rename (ADR-0006, no aliases) never reached, while the page's own Cloud
Environments command table directly above it already uses the post-rename
vocabulary.

The noun is verified against the command's behaviour, not just the
neighbouring text: in `packages/cli/src/commands/environments/bind.ts`,
`--build` spawns `compile --output <artifact>` and the write that follows
is `client.projects.update(<environment-id>, { metadata })` — a PATCH of
the environment record's `artifact_path`. The thing updated after the
compile is the environment, so `environment` is the accurate noun and
not merely the mechanically renamed one.


Claude-Session: https://claude.ai/code/session_01UjM2ia8Av1v5NqfqQEQmC6

Co-authored-by: Claude <noreply@anthropic.com>

Author: yinlianghui

content/docs/deployment/cli.mdx

@@ -1529,7 +1529,7 @@ os environments bind <environment-id> --artifact ./dist/objectstack.json
 os environments bind <environment-id> --artifact ./dist/objectstack.json --build
 ```
 
-`--build` runs `objectstack compile` before updating the project. `--reseed`
+`--build` runs `objectstack compile` before updating the environment. `--reseed`
 is reserved for the server-side reseed endpoint; use it only when that endpoint
 is available in your deployment.