Stable-Only: CI: Force install an appropriate openstacsdk version

Ansible has a weird constraint, of < 0.100.0, and doesn't recognize
openstacksdk 0.101.0 or newer for some versions of ansible. While
others, don't recognize versions newer than 1.0.0.

As such, our only real choice is to force lock the version to
a more version/cycle appropriate version to ensure compatability
since we also can't constain via requirements at this point.

Additionally, as a result of change I7b9c70b03c17c631da8e53f70808fed103c95c06
and the fact that the base issue broke metalsmith CI, we need to merge
that change in with this one.

Change-Id: Id258b294972c2f5ea816cb274773b8947f92e110
Co-Authored-By: Harald Jensås <hjensas@redhat.com>

metalsmith_ansible/roles/metalsmith_deployment/defaults/main.yml

@@ -18,4 +18,4 @@ metalsmith_traits: []
 metalsmith_user_name: metalsmith
 
 # Wait parameters
-metalsmith_provisioning_timeout:
+metalsmith_provisioning_timeout: 3600

playbooks/integration/initial-setup.yaml

@@ -23,6 +23,18 @@
       vars:
         ansible_python_interpreter: /usr/bin/python3
 
+    - name: Install the latest sdk to align with ansible
+      pip:
+        name: openstacksdk
+        state: latest
+      become: true
+      environment:
+        # NOTE(dtantsur): https://github.com/pypa/setuptools/issues/2353
+        SETUPTOOLS_USE_DISTUTILS: stdlib
+      vars:
+        ansible_python_interpreter: /usr/bin/python3
+
+
     - name: Install metalsmith
       pip:
         name: "{{ metalsmith_src_dir }}/metalsmith"