Pyqwe

- bug fix - default value of `__env_ignore__` set to False

- Added `pyqwe[dotenv]` optional extra functionality into `pyqwe`
- Added advanced settings to change how env vars are loaded

pyqwe not has 'settings keys'


[tool.pyqwe]
__env_ignore__ = false
__env_marker_start__ = "{{"
__env_marker_end__ = "}}"
__env_files__ = [".env.example"]


These can be used to configure how pyqwe reads, and deals with environment variables.

**Here's the updated readme section:**

**Using environment variables**

To use environment variables in the command, use the `{{ }}`
markers, these markers are the default but can be changed.

pyqwe will evaluate any environment variables that are set before running any commands.

If pyqwe detects an environment variable that is not set, it will raise an error. An error will
also be raised if environment variables are detected, and you do not have `python-dotenv` installed.

Here's an example of setting an environment variable in a command:

toml
[tool.pyqwe]
talk = "*shell:echo {{MESSAGE}}"


You can change the environment variable markers by changing the `__env_marker_start__` and `__env_marker_end__` settings
keys.

toml
[tool.pyqwe]
__env_marker_start__ = "*"
__env_marker_end__ = "*"
talk = "*shell:echo *MESSAGE*"


pyqwe uses `load_dotenv()` from `python-dotenv` to load the `.env` file. You can change the name of the file to load, or
add multiple env files by setting the `__env_files__` settings key.

toml
[tool.pyqwe]
__env_files__ = [".env", ".env.local"]
talk = "*shell:echo *MESSAGE*"


This is the same as running `load_dotenv(".env")` and `load_dotenv(".env.local")`.

If you want to disable pyqwe from doing anything with environment variables, you can set the `__env_ignore__` settings
key to `true`.

toml
[tool.pyqwe]
__env_ignore__ = true
talk = "*shell:echo {{MESSAGE}}"


This will disable the environment variable evaluation and loading of the `.env` file, and result in `{{MESSAGE}}` being
printed to the console in this case.

- Fixed CLI coloring in menus
- Added new group runner mode `step`


[tool.pyqwe]
group = [
"step",
"*:echo 'Hello, World! 1'",
"*:echo 'Hello, World! 2'",
"*:echo 'Hello, World! 3'"
]


results in:


🟢🏎💨🛑🏎 Starting runners in STEP (ctrl + c to abort)

🚥|🏎️ About to start runner:
*:echo 'Hello, World! 1'
Continue? [Y/n]: y
🏎💨 Starting runner
Hello, World! 1
🏁🏎 Runner done

🚥|🏎️ About to start runner:
*:echo 'Hello, World! 2'
Continue? [Y/n]: n
🚧🏎 Runner skipped

🚥|🏎️ About to start runner:
*:echo 'Hello, World! 3'
Continue? [Y/n]:

You can now specify how grouped runners should run, either in sequence or parallel.

This will run the commands in the group in sequence, one after the other:

toml
group = [
"sync",
"*:echo 'Hello, World! 1'",
"*:echo 'Hello, World! 2'",
"*:echo 'Hello, World! 3'"
]


This will run the commands in the group in parallel:

toml
group = [
"async",
"*:echo 'Hello, World! 1'",
"*:echo 'Hello, World! 2'",
"*:echo 'Hello, World! 3'"
]


Of course, you can leave out the `sync` or `async` to use the default async mode.

Commands can be grouped and run as one using threading.

toml
[tool.pyqwe]
group = [
"flask_example.module:run",
"*:gunicorn flask_example.package:create_app()",
"*:flask --app flask_example/package run --port 5003"
]


Running `pyqwe group` results in:


🏎💨🏎💨🏎💨 Starting runners
[2024-09-07 09:55:00 +0100] [35190] [INFO] Starting gunicorn 23.0.0
[2024-09-07 09:55:00 +0100] [35190] [INFO] Listening at: http://127.0.0.1:8000 (35190)
[2024-09-07 09:55:00 +0100] [35190] [INFO] Using worker: sync
[2024-09-07 09:55:00 +0100] [35191] [INFO] Booting worker with pid: 35191
* Serving Flask app 'flask_example.module'
* Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on http://127.0.0.1:5000
Press CTRL+C to quit
* Serving Flask app 'flask_example/package'
* Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on http://127.0.0.1:5003
Press CTRL+C to quit


Pressing `ctrl` + `c` will stop all runners as one.


^C 🏁🏎🏎🏎 Runners stopped
[2024-09-07 09:56:35 +0100] [35190] [INFO] Handling signal: int
[2024-09-07 09:56:35 +0100] [35191] [INFO] Worker exiting (pid: 35191)
[2024-09-07 09:56:35 +0100] [35190] [INFO] Shutting down: Master


This tool is intended only to be used in a development environment, say if you want to run Flask + Vite, or Flask + Tailwindcss in one process.

update pyproject description