Composer memory limit issues.

[a-username]

This was brought up the other day and confirmed across the team as an issue. I'm seeing it on a project as well. Whereas its most likely tied to slow dependency resolution issues and may be good to see occasionally as a red flag that something needs to be updated because it's take multiple passes to find the right dependencies, it's also a pain since we rarely have time on client work to do that (and for clients working directly with the Docker containers this is just buggy).
Any chance we can put something like:

RUN echo "memory_limit=-1" > /usr/local/etc/php/conf.d/memory-limit.ini

In the Dockerfiles? I've tested it on the project I'm working on and running composer install --profile -vvv shows that it's now able to go through the multi-pass dependency check without getting stuck. Totally open to just continuing with the current environment variable COMPOSER_MEMORY_LIMIT=-1 [composer command] solution since implementing this would be more about convenience than anything else.

[chrismshelton]

Hmm... I think we want to keep the memory limit in place, so there aren't any "works for me locally" memory limit issues that pop up when we push something live. How about this instead?

ENV COMPOSER_MEMORY_LIMIT "-1"