Ensure the path contains the Ozy bin directory when running anything through Ozy

[yeetfield]

Tested by removing ~/.ozy/bin/ from my path and running a binary which activated the conda installer.

On main, this produces:

Running conda installer for [binary]
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/installers/installer.rs:28:38
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

And on this branch it works.

[apmorton]

This isn't exactly what I was thinking - but maybe its better?

I was thinking we add the path explicitly for subprocesses when we are installing thing using ozy - not when transparently passing through to actual apps.

@mattgodbolt thoughts on unconditionally prepending the ozy path like this?

[yeetfield]

I think in the interest of keeping the critical path light, I'd prefer to do it the way you've recommended. It should be straightforward to move this into App::ensure_installed

[mattgodbolt]

No strong opinions here - I can't think there'd be any downsides to unconditionally prepending though.

[apmorton]

This doesn't do it "only when installing" - this adds it to the current processes environment when it happens to be installing, which then means it's sometimes added to the real apps path - which is worse than either of the options.

We should either:

• always add it
• add it only to the child processes launched by run_subcommand_for_installer

If nobody can come up with a real world downside to prepending it always, let's just do that like you had originally.