Setenv in env with broken deployment

### Description

Application includes `Dockerrun.aws.json` with `AWSEBDockerrunVersion: 3` and `docker-compose.yml`.
`docker-compose.yml` uses env variable from `.env`.

### Steps to reproduce

Deployment looks as follows:

```
eb init
eb create
eb setenv $(cat '.env')
eb deploy
```

Env is broken: `eb deploy` fails. But I can't do redeploy because `eb setenv` fails. `eb setenv` somehow consider that it should re-reploy right now without uploading the new version using `eb deploy`. The full list of invocations is the following:

```
eb terminate
eb init
eb create
eb setenv $(cat '.env')
eb deploy # fails
# now trying to redeploy
eb setenv $(cat '.env') # fails
```

### Observed result

`eb setenv` tries to redeploy the current app version that should not be redeployed. There is no option to turn off this _logic_. It is not possible to move `eb deploy` before `eb setenv`, because `docker-compose.yml` depends on env.

### Expected result

`eb setenv` should have an option to turn off the redeployment madness. Users should be able to set env without redeployment.

### Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS: Ubuntu 25.10
2. EBCLI version: 3.25

PS there is a workaround: `eb setenv --timeout 0`. It allows not waiting for silly redeployment, but redeployment will still be done in background. BTW `eb deploy` after `eb setenv --timeout 0` will wait until this silly redeployment will be done.

Reproduce the deployment using Dockerrun.aws.json, docker-compose.yml, and the eb init/create/setenv/deploy sequence, including the documented --timeout 0 workaround. Trace how eb setenv handles environment updates and redeployment; done means users can set environment variables without forcing redeployment, while eb deploy still behaves correctly.

Written by the indexing model from the issue text.