Feature: .ddev/.env.<anything> or .ddev/.env.global.<anything>

[rfay]

Feature Request

We might want to have a way to use a unique .ddev/.env.* file for particular applications.

This specifically relates to

• Improve Craft CMS "settings management" (writing to project .env) #7233

They would like a Craft-specific .env that is not in the application space. It's a good idea and would improve all the CMSs that use .env, and we wouldn't be writing their file or really needing the #ddev-generated as much, although we can still request it.

Currently .ddev/.env works great for all containers, and .ddev/.env.* refers to a particular container name like .ddev/.env.solr

[stasadev]

Think about how we should gitignore these .env files in the .ddev/ directory.