Exit from bestpath early if there's only 1 path to evaluate

[taspelund]

No description provided.

[taspelund]

test-interop job is failing now because jq installed or in $PATH on juniper/arista VMs... not sure why this worked before but is broken now, but I'll look into it

[taspelund]

I am able to reproduce the "missing jq" symptom when running interop on my workstation.
It would appear this is due to an issue with Debian's bullseye-backports repo causing it to return a 404 when apt attempts to look for its Release file: https://github.com/oxidecomputer/testbed/issues/158

[rcgoodfellow]

LGTM. Thanks @taspelund

[taspelund]

Pretty sure this latest CI failure is because I updated the init.sh scripts for debian/arista nodes in a4x2 but forgot to update it for arista/juniper in interop. Will submit a testbed PR to address it, which should let this pass.

[taspelund]

I think this is ready to merge once we have the interop tests passing. I re-ran test-interop and it's failing because the /input directory populated by buildomat is empty:

2025-08-27T21:28:16.077Z	+ find /input -ls
2025-08-27T21:28:16.077Z	   34    1 drwxr-xr-x   2 root     root            2 Aug 27 21:28 /input
...
2025-08-27T21:31:31.031Z	+ tar xvfz /input/build-interop/work/testbed.tar.gz
2025-08-27T21:31:31.031Z	tar: /input/build-interop/work/testbed.tar.gz: No such file or directory

Not sure if this is a known thing, or maybe there's a lifetime to how long buildomat will retain artifacts from old jobs?

[rcgoodfellow]

Since there have been substantial updates to the machinery underpinning interop, i would run the whole build/test job combo again, or just push an empty commit to this PR to running all of CI fresh.