Use environment variables to control Ansible

Ansible configuration can be managed by an `ansible.cfg` ini file, but
setting up that file and ensuring it's always in the same place is
difficult.

Configure Ansible via environment variables instead.

Signed-off-by: Major Hayden <major@redhat.com>

schutzbot/Jenkinsfile

@@ -4,6 +4,18 @@ pipeline {
     environment {
         AWS_REGION = "us-east-2"
         AWS_BUCKET = "imagebuilder-jenkins-testing-use2"
+        // Colorful Ansible always looks nicer.
+        ANSIBLE_FORCE_COLOR="True"
+        // Time each task and display stdout as YAML (easier to read).
+        ANSIBLE_LOAD_CALLBACK_PLUGINS="True"
+        ANSIBLE_CALLBACK_WHITELIST="profile_tasks"
+        ANSIBLE_STDOUT_CALLBACK="yaml"
+        // Don't display those ugly purple deprecation warnings.
+        ANSIBLE_DEPRECATION_WARNINGS="False"
+        // Our host keys are constantly changing.
+        ANSIBLE_HOST_KEY_CHECKING="False"
+        // Enable ssh pipelining for faster deployments to remote nodes.
+        ANSIBLE_PIPELINING="True"
     }
 
     options {