Debug output on all molecule commands

[mdpdesign]

Issue Type

• Bug report

Molecule and Ansible details

ansible 2.10.3
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/mdp/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/mdp/ansible-roles/molecule-venv/lib/python3.6/site-packages/ansible
  executable location = /home/mdp/ansible-roles/molecule-venv/bin/ansible
  python version = 3.6.9 (default, Oct  8 2020, 12:12:24) [GCC 8.4.0]
molecule 3.2.1.dev1 using python 3.6
    ansible:2.10.3
    delegated:3.2.1.dev1 from molecule
    vagrant:0.5.dev1 from molecule_vagrant

Molecule installation method (one of):

• pip

Ansible installation method (one of):

• pip

Desired Behavior

Molecule should output at most the INFO log messages when running commands without --debug

Actual Behaviour

For all commands like list, create, verify molecule outputs some DEBUG log along side the INFO without explicitly using --debug switch. IMHO debug output should be only showed when using --debug switch - unless this is intended?

For command: molecule list

DEBUG    Validating schema /home/mdp/ansible-roles/jenkins_swarm/molecule/default/molecule.yml.
DEBUG    Validating schema /home/mdp/ansible-roles/jenkins_swarm/molecule/service/molecule.yml.
DEBUG    Validating schema /home/mdp/ansible-roles/jenkins_swarm/molecule/vmware/molecule.yml.
INFO     Running default > list
INFO     Running service > list
INFO     Running vmware > list
                    ╷             ╷                  ╷               ╷         ╷
  Instance Name     │ Driver Name │ Provisioner Name │ Scenario Name │ Created │ Converged
╶───────────────────┼─────────────┼──────────────────┼───────────────┼─────────┼───────────╴
  win10             │ vagrant     │ ansible          │ default       │ false   │ false
  win12             │ vagrant     │ ansible          │ default       │ false   │ false
  win10-svc         │ vagrant     │ ansible          │ service       │ false   │ false
  win12-svc         │ vagrant     │ ansible          │ service       │ false   │ false
  jsw-win10-schtask │ delegated   │ ansible          │ vmware        │ true    │ true
  jsw-win10-svc     │ delegated   │ ansible          │ vmware        │ true    │ true
  jsw-win12-schtask │ delegated   │ ansible          │ vmware        │ true    │ true
  jsw-win12-svc     │ delegated   │ ansible          │ vmware        │ true    │ true
                    ╵             ╵                  ╵               ╵         ╵

or for molecule create -s vmware

DEBUG    Validating schema /home/mdp/ansible-roles/jenkins_swarm/molecule/vmware/molecule.yml.
INFO     vmware scenario test matrix: dependency, create, prepare
INFO     Running vmware > dependency
DEBUG    Using selector: EpollSelector
Starting galaxy role install process
- changing role lean_delivery.java from 7.1.0 to 7.1.0
- extracting lean_delivery.java to /home/mdp/.cache/molecule/jenkins_swarm/vmware/roles/lean_delivery.java
- lean_delivery.java (7.1.0) was installed successfully
INFO     Dependency completed successfully.
WARNING  Skipping, missing the requirements file.
INFO     Running vmware > create
WARNING  Skipping, instances already created.
INFO     Running vmware > prepare
WARNING  Skipping, instances already prepared.

Also if I may suggest, I think WARNING outputs should be rather colored in yellow instead of red (suggesting visually that something failed)