Set global flags via global mechanisms (environment variable, config file)

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

When integrating poetry in a larger work of development loop automation and build system pipeline the same command will get run in different contexts.

As such some options would be better served if we could put them in configuration directly instead of having to modulate the command line calls.

Thus when running the script in an interactive session on the programmer's station poetry commands would be interactive with ansi coloring. but the very same script when run on an unattended build system would automatically receive --no-ansi --no-interaction global options if these were added in the poetry config already present on the build machine / docker image.

Same goes with the quiet and verbose flags and any other options that could affect all commands.

thanks

Start by reviewing how Poetry commands currently receive global options such as --no-ansi, --no-interaction, quiet, and verbose, then compare that with the existing poetry config used on build machines and Docker images. Define how environment variables or configuration should apply across commands, including precedence and interactive versus unattended execution, before identifying implementation entry points and tests.