Bug 2142803

Description of problem:

'ansible_verbosity' setting keeps flipping between 0 (default, zero verbosity) and 1.

In other words, if you run `hammer settings set --name "ansible_verbosity" --value 0` Satellite will eventually override the value to 1,2,3 or 4 (depends which verbosity setting was last set).

Same thing happens if the verbosity is set via WebUI:
- Administer --> Settings --> Ansible --> Default verbosity level --> Disabled

Following script is a reproducer:

# cat ansible_verbosity.sh
~~~
#!/bin/bash

(date && hammer settings set --name "ansible_verbosity" --value 1) >> foreman_settings_set.txt
sleep 10
(date && hammer settings set --name "ansible_verbosity" --value 0) >> foreman_settings_set.txt

while true; do
  (date && hammer settings show --name "ansible_verbosity") >> foreman_settings_status.txt
  (date && sudo su - postgres -c "psql -d foreman -c 'select * from settings where id=XXX;'") &>> postgres_settings_status.txt
  sleep 10
done
~~~


This leads to ansible roles/playbooks being run in random verbose levels.