Molecule not using virtualbox with vagrant

Hello

I have a problem.

I want to use moelcule with virtualbox

My config:

```
11:07:09 mabed@tower ~ → vagrant -v ; vagrant plugin list
Vagrant 2.2.19
vagrant-libvirt (0.7.0, system)
virtualbox (0.8.6, global)

11:07:24 mabed@tower ~ → neofetch
.',;::::;,'. mabed@tower
.';:cccccccccccc:;,. -----------
.;cccccccccccccccccccccc;. OS: Fedora Linux 37 (KDE Plasma) x86_64
.:cccccccccccccccccccccccccc:. Host: MS-7D25 2.0
.;ccccccccccccc;.:dddl:.;ccccccc;. Kernel: 6.1.8-200.fc37.x86_64
.:ccccccccccccc;OWMKOOXMWd;ccccccc:. Uptime: 13 hours, 38 mins
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:. Packages: 2337 (rpm)
,cccccccccccccc;MMM.;cc;;WW::cccccccc, Shell: bash 5.2.15
:cccccccccccccc;MMM.;cccccccccccccccc: Resolution: 1920x1080
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc: Terminal: /dev/pts/1
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc; CPU: 12th Gen Intel i7-12700K (20) @ 4.900GHz
ccccc:XM0';cccc;MMM.;cccccccccccccccc' GPU: NVIDIA GeForce GTX 1080
ccccc;MMo;ccccc;MMW.;ccccccccccccccc; GPU: Intel AlderLake-S GT1
ccccc;0MNc.ccc.xMMd:ccccccccccccccc; Memory: 3884MiB / 31878MiB
cccccc;dNMWXXXWM0::cccccccccccccc:,
cccccccc;.:odl:.;cccccccccccccc:,.
:cccccccccccccccccccccccccccc:'.
.:cccccccccccccccccccccc:;,..
'::cccccccccccccc::;,.

```

Molecule:

```
---
dependency:
name: galaxy
driver:
name: vagrant
provider:
name: virtualbox
provision: yes
parallel: true
platforms:
- name: debian-testing
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: debian/testing64
memory: 1024
cpus: 1
- name: debian-11
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/debian11
memory: 1024
cpus: 1
- name: debian-10
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/debian10
memory: 1024
cpus: 1
- name: ubuntu-2204
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/ubuntu2204
memory: 1024
cpus: 1
- name: ubuntu-2004
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/ubuntu2004
memory: 1024
cpus: 1
- name: ubuntu-1804
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/ubuntu1804
memory: 1024
cpus: 1
- name: fedora-37
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/fedora37
memory: 1024
cpus: 1
- name: fedora-36
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/fedora36
memory: 1024
cpus: 1
- name: centos-7
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/centos7
memory: 1024
cpus: 1
- name: openbsd-7
config_options:
ssh.keep_alive: yes
ssh.remote_user: 'vagrant'
synced_folder: true
box: generic/openbsd7
memory: 1024
cpus: 1
provisioner:
name: ansible
verifier:
name: testinfra
scenario:
name: "vm"
test_sequence:
- "lint"
- "destroy"
- "dependency"
- "syntax"
- "create"
- "prepare"
- "check"
- "converge"
- "idempotence"
- "check"
- "side_effect"
- "verify"
- "destroy"
```

Molecule try to download libvirt box and not use virtuabox box...µ

```
==> fedora-36: Box download is resuming from prior download progress
Progress: 0% (Rate: 0*/s, Estimated time remaining: --:--:--)==> openbsd-7: Adding box 'generic/openbsd7' (v4.2.10) for provider: libvirt
Progress: 0% (Rate: 0*/s, Estimated time remaining: --:--:--) openbsd-7: Downloading: https://vagrantcloud.com/generic/boxes/openbsd7/versions/4.2.10/providers/libvirt.box
```

Pipfile:

```
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[dev-packages]
python-vagrant = "*"
ansible-lint = "*"
molecule = "*"
molecule-plugins = "*"
"molecule-plugins[podman]" = "*"
"molecule-plugins[vagrant]" = "*"

[packages]
ansible = "7"

[requires]
python_version = "3"
```

Can you help me

Start by reproducing the issue with the provided Molecule configuration and Pipfile, then inspect how the Vagrant provider and installed molecule-plugins[vagrant] select a box provider. Done means the configured VirtualBox provider is used instead of downloading the libvirt boxes; the payload names no repository files or tests.

Written by the indexing model from the issue text.