.env file not created when using --dont-exe-cf, creates confusing ux and errors later

[shortjared]

This was a confusing user experience raised by @zoonywhoop.

If you create a new project, using our own suggested best practices of --dont-exe-cf with a Power User for deploys, and using an Admin via the UI to create the resources, an env file doesn't not get initialized in the bucket.

This ends up being very confusing because now all deploys fail for the stage because an env file does not exist. And to make matters even worse env set also fails because it can't pull the env file to begin with. 😦