feat(config): Add option for env_path

[altugbakan]

Implements #5723

Motivation

Now, the .env file is only loaded from the project root. A config option can be added to load the .env file from another directory. This will be helpful if Foundry is used within a monorepo that uses a single .env file.

Solution

I have added an option for the config to allow adding the env_file location. Since it will not change often, I thought making it a config item instead of a CLI flag would make more sense.

[mattsse]

not entirely opposed to this because I can see how this is useful.
but this has the same effect as doing a source call, which I guess is cumbersome if you need to change env vars often?

would it be possible to symlink the env file in the foundry root dir?

[mattsse]

I'd like to keep this function as is

[mattsse]

this complicates things a lot, because is an additional config lookup, which isn't super cheap.

I also don't want to automatically load env vars when loading the config.
so not quite sure yet where to apply this

[altugbakan]

not entirely opposed to this because I can see how this is useful. but this has the same effect as doing a source call, which I guess is cumbersome if you need to change env vars often?

would it be possible to symlink the env file in the foundry root dir?

Makes sense, I agree that this is kind of hard to implement with this structure. I will try and see how it goes.

[altugbakan]

@mattsse where do you think would be a good place in code for checking if env_root exists and create the symlink?