Config Scripts - Autocomplete issue with --conf parameter prevents script startup

[david-hummingbot]

Describe the bug

There is a bug with the configurable scripts where using the --conf parameter causes an autocomplete feature to activate. This issue occurs specifically when the default configuration filename begins with "conf" (e.g., "conf_strategy_name.yml"). When typing a command like start --script v2_strategy_config.py --conf, the autocomplete pop-up is triggered immediately after --conf is input, and when selecting the config file it appends the filename to the parameter leading to a prevention of the script from starting up as expected.

Steps to reproduce

1. Ensure there is at least one configuration file in the directory whose name starts with "conf".
2. Launch HB.
3. Type the command start --script any_v2_config_strategy.py --conf
4. Observe that the autocomplete pop-up is triggered immediately after --conf
5. Select the config file and observe an error in the log and the script is unable to start

Release version

dev-1.24.0

Type of installation

Source

Attach required files

[nikspz]

reproduced only if you paste whole start --script any_v2_config_strategy.py --conf (without spacebar in the end), so minor issue.

If you do all type manually, not reproduced