Drush Launcher is dead, the default Drush binary path should be the path of Drush binary installed at the project level

[mxr576]

A quote from similar issues about the deprecation of Drush Launcher.

Triggered by the recent presentation on DrupalCon Pittsburg.

Drush 11 got an EOL date: 2023 November. It was also marked as not recommended for Drupal 10. The recommended version is Drush 12.

Drush Launcher is not (officially) compatible with Drush 12 at this moment and it may not be compatible in the future, rather Drush 12 is going to fail nicely when it is called via Drush Launcher: https://github.com/drush-ops/drush-launcher/issues/105

[mxr576]

In theory this approach could be used to dynamically find the project specific bin directory and the drush instance inside

https://getcomposer.org/doc/articles/vendor-binaries.md#finding-the-composer-bin-dir-from-a-binary