Correct code example for CLI auth with env variable

[blvckcoffee]

Description

• Updates code example and text for CLI password authentication after setting TRINO_PASSWORD environment variable
• Current behavior requires --password in CLI code snippet even after setting the TRINO_PASSWORD environment variable. If --password is not provided, trino CLI will appear to start without CLI prompt for password, but running SQL results in "Error running command: Authentication failed: Authentication required"

Additional context and related issues

• Fix --password option for CLI documentation #17402

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

[blvckcoffee]

Tested functionality with @mosabua. Trino docs should reflect that --password is required to avoid authentication error messaging.

[mosabua]

The real problem is that even with TRINO_PASSWORD set a user must use --password so the value is used. If --password is not used .. the value is NOT used and the CLI starts through and gets to the trino> prompt .. but then running any query fails. This is a bad user experience and in my opinion a bug in the code. Could you check and fix @electrum .. and maybe we merge the docs now anyway since the current docs are incorrect?

[mosabua]

Could you please review and confirm @electrum ?

[mosabua]

Discussed and confirmed on slack with @electrum

[ebyhr]

@blvckcoffee I would recommend using reserved keywords (e.g. fixes #xxx) in PR description so that we can close the issue automatically. https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests

[mosabua]

Thanks for picking that up @ebyhr .. I was under the wrong impression that "Fix" also does the job..