```pixi workspace export conda-environment``` should handle environment variables

[sdvillal]

Problem description

At the moment, exporting environments to conda.yml files would not export any defined variables to the environment.

Here you can see a brittle workaround here.

I guess logic is not as simple as it sounds, as variables could be defined on the basis of pixi-only environment. I would argue:

• Any variable that is a literal or depends on conda standard variables (e.g., CONDA_PREFIX) should be exported as is.
• Variables depending on pixi variables should still be exported but throw a warning (or assume default location and define in terms of CONDA_PREFIX where possible).

Or, to make it easy, we could just export everything as defined.

xref: aqlaboratory/openfold-3#34

[ruben-arts]

I think all the activation.env variables could relatively easiliy be added to the these conda environment yamls. I'm open to contributions!

The Pixi code allows you to request the activation.env data on an environment so it should be easy to add:

pixi/crates/pixi_core/src/workspace/environment.rs

Lines 318 to 325 in 19d4257

	pub(crate) fn activation_env(&self, platform: Option<Platform>) -> IndexMap<String, String> {
	self.features()
	.map(|f| f.activation_env(platform))
	.fold(IndexMap::new(), |mut acc, env| {
	acc.extend(env.iter().map(|(k, v)| (k.clone(), v.clone())));
	acc
	})
	}

[SrisharanVS]

Hi @ruben-arts Can you assign this to me? I'm willing to work on this issue.