Use standard naming of some binaries (yosys-uhdm, zachjs-sv2v)

[hzeller]

The intent of sv-tests is not only to run with the locally compiled runners but as well with the binaries available on the machine and available in the PATH.

Some binaries stand out

yosys-uhdm

(there was a time when yosys-uhdm and yosys needed to be differently as the former required some patches. But not anymore for the last year or so)

On a regular users's machine, this will be just yosys that then uses the systemverilog plugin locally and runs with that.
So ideally, the yosys-uhdm runner would just invoke yosys (which then uses the installed systemverilog plugin).

This could be solved two different ways: in the simplest case we continue as-is, but decide to run yosys-uhdm if that is in the path and yosys as fallback otherwise.

Preferably though have the compilation of yosys indeed only happen once and then add the systemverilog plugin compiled and linked against the locally built yosys. That way we always make sure to actually compare the same version of yosys, just that in one runner we use the systemverilog plugin.

zachjs-sv2v

On a regular machine, this binary would just be called sv2v instead of zachjs-sv2v. I remember the current name came from some potential name clash, but don't remember the details.