Pre-script password handling possibly broke on Tahoe 26.6.2

For quite a long time I have been using this kind of pre-script to connect to AWS RDS without any issues

```bash
AWS_PROFILE=my-profile

AURORA_URL=$(aws rds describe-db-clusters --query "DBClusters[?DBClusterIdentifier == 'my-cluster'].Endpoint" --output text --profile $AWS_PROFILE)

PGPASSWORD="$(aws rds generate-db-auth-token --hostname $AURORA_URL --port 5432 --username my-user --profile $AWS_PROFILE)"

echo $PGPASSWORD
```

I have RDS tunnel set and open and that works. When connecting from Postico with the pre-script I get the error

`connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: PAM authentication failed for user "my-user"`

Now if I run the script in console, copy paste the password into the Postico password field and turn off the pre-script I can connect without issues. Yesterday I installed the Tahoe 26.6.2 and am now facing this odd issue. Any idea what might have changed or what is causing this? Is there a way to debug and see what password postico is trying to use when connecting?

-----

Postico 2: 2.3.3 (9804)
MacOS: 26.6.2

Start with Postico 2.3.3’s pre-script connection flow on macOS 26.6.2, using the supplied Bash script and RDS tunnel. Compare a connection using the script with one using the copied token, and capture connection diagnostics without exposing credentials. Done means identifying whether Postico passes the pre-script password correctly or documenting the environment-specific cause.

Written by the indexing model from the issue text.