Dotenv for docker compose

[bigstones]

Motivation and context

• related issues
  use .env for docker compose environment #7311

When I use CVAT with Docker Compose, I find it necessary to remember which version of CVAT I am using. However, I suggest maintaining CVAT versions and any customizations in a .env file, as it could reduce the number of properties that need to be remembered.

In the current commit, only CVAT VERSION and HOST are included, but I think it might be beneficial to gradually expand this functionality.

Please let me know your thoughts.

Thank you.

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have created a changelog fragment
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (see GitHub docs)
  use .env for docker compose environment #7311
• I have increased versions of npm packages if it is necessary
  (cvat-canvas,
  cvat-core,
  cvat-data and
  cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.