fix: (follow-up) use original interpreter path as 'home' value in pyv…

[honnix]

…env.cfg

This is a follow-up of #226 to fix another place.

---

Type of change

• Bug fix (change which fixes an issue)

For changes visible to end-users

• Suggested release notes are provided below:

Ensure correct home pathing is used when generating the venv.

Test plan

• Manual testing; please provide instructions so we can reproduce:

As described by #226 (comment)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[mattem]

Thanks @honnix, are you able to sign the CLA?

[honnix]

Thanks @honnix, are you able to sign the CLA?

I will have to go through my employer so not sure how long it would take. Please feel free to pick up the change and discard this PR, as it is so small anyway :)

[honnix]

@mattem This is a somewhat annoying bug. To unblock the fix I will close this PR and please help fix it. Thank you!

[honnix]

Looks like this has not been solved. Could you please help fix it @mattem ? Thank you. NVM I got lost in recent changes.