Recent GHA/VirtualBox issues

[acj]

Something changed a couple of weeks ago that is causing FreeBSD guest VMs to fail on GitHub Actions. I don't know whether the change was in GHA or VirtualBox or something else, but it's resisted my troubleshooting. The most common behavior is that the VMs cause the runner to hard-fail and not produce any useful logging.

The good news is that there are a couple of workarounds:

1. Switch to libvirt/kvm as the virtualization manager instead of VirtualBox. This provides a significant speedup and is fast enough that we won't need this base box anymore. The only downside that I'm aware of is that on some GHA runners with Intel Xeon CPUs, libvirt throws an error like this: "Error saving the server: Call to virDomainDefineXML failed: invalid argument: could not get preferred machine for /usr/bin/qemu-system-x86_64 type=kvm".
2. Use vmactions/freebsd-vm, which was just revamped to use qemu. They had a similar issue with machines failing to boot. Early reports say that the qemu approach is working well.

I've updated rbspy and proc-maps to use option 1.

With better options available now, I'm thinking about archiving this repo.

cc @benfred - I would guess that py-spy CI is struggling in the same way.

[benfred]

Thanks @acj! I've been hitting the same issues in py-spy with freebsd CI - and have had to re-run several times to get a successful run on recent PR's.

I'm going to try out option 1 with py-spy and remoteprocess, and will let you know how its going

[benfred]

I've changed over remoteprocess and py-spy to match rbspy/proc-maps.

This really sped up the freebsd ci - and seems to be improving the reliability. Thanks!