hack/ci: pass --remote to bud tests

[vtushar06]

The bud remote job runs the same local binary as bud local. Both jobs from run 31847250452 on main print the identical bats invocation:

sudo env TMPDIR=/var/tmp PODMAN_BINARY=/var/tmp/podman-container-tools/podman/bin/podman PODMAN_SERVER_LOG= REMOTE= ...

bin/podman, not podman-remote, and REMOTE= empty, in the job named remote.

The remote path in run-buildah-bud-tests is gated on PODBIN_NAME (line 78), which Cirrus used to set per matrix task. The migration replaced that with a mode: matrix key, but run_bud() never reads $MODE - run_int, run_sys, run_machine and run_upgrade all do. grep -rn PODBIN_NAME outside vendor finds it only inside run-buildah-bud-tests itself and in the treadmill script's Cirrus text.

So apply-podman-deltas has 30 skip_if_remote and 4 skip_if_rootless_remote entries that are currently no-ops, and podman-remote build coverage has been off since the migration.

--remote is already an option on the script and sets PODBIN_NAME=remote before that gate, so this is one branch in run_bud.

Worth saying plainly: this restores coverage rather than being a no-op, so the remote leg may go red on things that have been hidden. Most of the historically broken ones should already be covered by those deltas, but if new failures show up I am happy to iterate on them here or in a follow-up.