molecule reset expects docker to be the driver and fails if it isn't

[jimboolio]

Testing with latest development version was mandatory for doing a bug report, so I'll report this issue here.

My molecule version:

molecule 6.0.2 using python 3.11 
    ansible:2.15.4
    azure:23.5.0 from molecule_plugins
    containers:23.5.0 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1
    default:6.0.2 from molecule
    docker:23.5.0 from molecule_plugins requiring collections: community.docker>=3.0.2 ansible.posix>=1.4.0
    ec2:23.5.0 from molecule_plugins
    gce:23.5.0 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0
    podman:23.5.0 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
    vagrant:23.5.0 from molecule_plugins

I'm using molecule-plugins[vagrant]

I got this from molecule destroy command:
The scenario config file ('/home/myuser/myrole/molecule/default/molecule.yml') has been modified since the scenario was created. If recent changes are important, reset the scenario with 'molecule destroy' to clean up created items or 'molecule reset' to clear current configuration.

So I ran molecule reset but it fails as follows:

$ molecule reset
WARNING  Driver vagrant does not provide a schema.
INFO     default scenario test matrix: 
INFO     Performing prerun with role_name_check=0...
INFO     Using /home/myuser/.ansible/roles/myorg.myrole symlink to current repository in order to enable Ansible to find the role using its expected full name.
INFO     Removing /home/myuser/.cache/molecule/myrole/default
Traceback (most recent call last):
  File "/home/myuser/venv/bin/molecule", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/myuser/venv/lib64/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/venv/lib64/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/home/myuser/venv/lib64/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/venv/lib64/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/venv/lib64/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/venv/lib64/python3.11/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/venv/lib64/python3.11/site-packages/molecule/command/reset.py", line 48, in reset
    driver.reset()
  File "/home/myuser/venv/lib64/python3.11/site-packages/molecule_plugins/docker/driver.py", line 256, in reset
    import docker
ModuleNotFoundError: No module named 'docker'

This issue is related and I think it contains the workaround: #2540