Just use the builtin "python -m venv" and life is good, why the others?
I tried almost all of them, with various issues, now staying with the default venv, it's solid and get the job done.
And then the same for your friend the buildserver.
It's all about reproducibility.
in the "worst" case you can always do a docker
So you actually need something that can read a specification of the required python version and use the correct one from the available options (maybe even reaching out and getting it if it isn't already locally available, though I don5 remeber if any of the existing python build tools will do this; docker obviously will, but its not really a python build tool), across different OS flavors (maybe not that last bit, depending on the use case, especially for internal development), and with minimal overhead for the build tool itself.