rework docker compose script to allow future extensibility

[piotrkwiecinski]

This is the first step to allow more flexibility.

For example instead of having blackfire commented out in main compose.yaml.
It could be moved to a separate file and included in the list when feature toggle is enabled.

Something like:

if [ ${BLACKFIRE_ENABLED} -eq 1 ]; then
  COMPOSE_FILES_LIST+=("compose.blackfire.yaml")
fi

It would allow adding features like #998 the same way.

[what-the-diff]

PR Summary

• Enhanced Support for Multiple Compose Files
  The new changes allow for the loading of multiple Docker compose files. These files are stored in an array called COMPOSE_FILES. This provides a more flexible and efficient way to manage multiple Docker compose files in the system.

• Optional Exclusion of the Development Configuration File
  The system has been improved to handle the --no-dev argument. Users can use this argument to exclude the development configuration file compose.dev.yaml when they do not want to use it.

• Enhanced Command Execution
  A new method for executing Docker compose commands has been put in place. It constructs command-line parameters dynamically, accommodating either single or multiple compose files. This increases efficiency and reliability when executing various commands.

[YPyltiai]

@piotrkwiecinski part of the reason I added Cloudflare to same file is to have it in same network as the rest of app. If you have it separately - I guess we'd manually need to set networks too. But good idea anyways!

[piotrkwiecinski]

It's going to be my next PR. I want to link services using network, so these changes are easier.

[markshust]

Just need a few comments here to explain what the code is doing. Thanks!

[markshust]

Thanks so much, great update!

[markshust]

This is all set and should be closed out 👍