forcecleanup build option does not fully work ⇒ aborting Jenkins build breaks subsequent build jobs

Someone, presumably a @foundations-team member, aborted jobs recently:

As an unfortunate consequences, all subsequent jobs run on the same isobuilder failed with:

Bringing machine 'default' up with 'libvirt' provider...
Name `tails-builder-amd64-bullseye-20211115-c3cd72dcc6default` of domain about to create is already taken. Please try to run
`vagrant up` command again.
rake aborted!

Jenkins enables the forcecleanup build option that is supposed to make our Rakefile handle this exact situation.

This problem also happens when Jenkins aborts a build because the corresponding Git branch was merged, and the corresponding job was therefore deleted, while a build was running.

Edited by intrigeri