Remove COMPOSE_MENU env from e2e tests

[jhrotko]

What I did
Removed COMPOSE_MENU from env in Dockerfile and Makefile
Related issue

(not mandatory) A picture of a cute animal, if possible in relation to what you did

[milas]

LGTM but tbh the more I think about it, it seems like we shouldn't need to specify COMPOSE_MENU / --menu for tests at all, I'd assume everything would be detected as NOT a TTY and thus not try to show the menu 🤔

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.76%. Comparing base (cc09f39) to head (4170c47).
Report is 25 commits behind head on main.

❗ Current head 4170c47 differs from pull request most recent head 769ec5a

Please upload reports for the commit 769ec5a to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11654      +/-   ##
==========================================
+ Coverage   54.52%   54.76%   +0.23%     
==========================================
  Files         145      145              
  Lines       12694    12585     -109     
==========================================
- Hits         6922     6892      -30     
+ Misses       5071     4999      -72     
+ Partials      701      694       -7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[glours]

I agree with @milas we should not have the --menu in e2e test, Compose should detect TTY isn't available when running e2e in CI

[ndeloof]

if removal for COMPOSE_MENU require --menu=false to be added to all our e2e test I'd prefer we keep the variable!