Fix breeze setup autocomplete references

[johnslavik]

The ./scripts/tools/setup_breeze script fails to install autocompletions. To reproduce:

Details

❯ which breeze &>/dev/null && rm -vf $(which breeze)
removed '/home/bswck/.local/bin/breeze'
 
❯ ./scripts/tools/setup_breeze 

The 'breeze' is not on path. Breeze should be installed and 'breeze' should be available on your PATH!

Installing Breeze. This will install breeze via uv and modify your /bin/bash to run it


Please confirm installing and modifying the startup scripts. Are you sure? [y/N/q]
y
The answer is 'yes'. installing and modifying the startup scripts. This can take some time!
Resolved 108 packages in 28ms
Uninstalled 1 package in 1ms
Installed 1 package in 7ms
 ~ apache-airflow-breeze==0.0.1 (from file:///home/bswck/Apache/airflow/dev/breeze)
Installed 1 executable: breeze
                                                                                                                                                                
 Usage: breeze [OPTIONS] COMMAND [ARGS]...                                                                                                                      
                                                                                                                                                                
                                                                                                                                                                
 Try running the '--help' flag for more information.                                                                                                            
                                                                                                                                                                
╭─ Error ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ No such command 'setup-autocomplete'.                                                                                                                        │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
                                                                                                                                                                
                                                                                                                                                                
 To find out more, visit https://github.com/apache/airflow/blob/main/dev/breeze/doc/01_installation.rst

In #25449, the setup-autocomplete command became setup autocomplete, but ${BREEZE_BINARY} setup-autocomplete in the setup script (which used to be ./breeze back then) wasn't fixed up -- 31fb5ff#diff-7e92c11499fd4106a899eeb457db8277bd6f09dd29e683f33ae704e12fa29caeR73. A trickier one :)

I've fixed the old-fashion command invocation, and I've corrected the remaining stale references to setup-autocomplete in the docs.

You shouldn't find setup-autocomplete now anywhere but in CSS class names.

cc @potiuk (hi! 😁)

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[johnslavik]

To follow up on this in the future, do you think it's worth it to cover this and similar paths of such setup scripts (and their examples in the docs) with some tests, just in case? I could file an issue to track.

[potiuk]

Nice.

[potiuk]

Interesting. Main reason why it was not working was that recently - in August - #54258 when I removed some very, very old deprecated commands (setup-autocomplete was something that was there initially and we had deprecated command still available till August).

To follow up on this in the future, do you think it's worth it to cover this and similar paths of such setup scripts (and their examples in the docs) with some tests, just in case? I could file an issue to track.

Actually this is one of the very few scripts not covered by CI - and I take it almost as a pride point to test all those scripts. This one has not been tested, because it was mostly a helper. But ABSOLUTELY .... Feel free to add it to our CI :)

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[potiuk]

Thanks my friend BTW. Glad to see you here :)

[github-actions]

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

[johnslavik]

Feel free to add it to our CI :)

🫡