Match subtlety of various paths in pyvenv.cfg?

[brettcannon]

If you look at what ends up in pyvenv.cfg, there's three things which contain paths:

1. home
2. executable
3. command

Now home and command do not resolve their sys.executable values, while executable does (some of this is inadvertently my fault 😅). The question is whether it is useful to disambiguate between the exact binary used to create the virtual environment or the path (i.e. the resolved path or the one that happened to be typed into the terminal)? From a reproducibility perspective, resolved paths are best as that is exactly what was used to create the virtual environment. From a recording perspective, though, you want what was specified, even if you were to reuse those values they could change (e.g. /usr/local/bin/python3 could now point to python3.12 instead of python3.11).

I'm not sure if full compatibility is more important or if it's best to take a stand?