fix: Make sure that environments are not completely overridden

[hameerabbasi]

Fixes #2383

[ruben-arts]

Thank you! The PR looks good from an implementation stand point!

However this will be a breaking change of the configuration.

Users would need to switch from:

[activation]
scripts = ["default.sh"]
[target.win-64.activation]
scripts = ["default.bat"]

To:

[target.unix.activation]
scripts = ["default.sh"]
[target.win.activation]
scripts = ["default.bat"]

To not have a broken experience.

I'll contact the team what we'll do with this.

[baszalmstra]

I get the implementation from the perspective of environment variables. I would indeed want to use the environment variables from all the targets and have them override each other based on environment variable name.

However, for activation scripts, I would not want to combine them. I think we should make this distinction is properly made.

Alternatively we could also change the scripts key to take a map instead of an array so you can have "named" scripts which can be individually overriden by different targets.

[hameerabbasi]

I get the implementation from the perspective of environment variables. I would indeed want to use the environment variables from all the targets and have them override each other based on environment variable name.

However, for activation scripts, I would not want to combine them. I think we should make this distinction is properly made.

Alternatively we could also change the scripts key to take a map instead of an array so you can have "named" scripts which can be individually overriden by different targets.

I do like the script map idea; it also occurred to me. However; my concern is that existing user configs would be broken by this.

[hameerabbasi]

I've reverted the changes to activation scripts in 720db9e; but kept ones for envs to get this in faster.

[ruben-arts]

Thank you for the contribution.