Use openstacksdk for most transitive depends

This should get openstacksdk on to people's machines in advance of
porting ansible modules to use sdk directly. It also lets us just use
sdk for all of the transitive depends.

Leave os-client-config as openstacksdk doesn't depend on it and
transitioning to openstack.config is a better task for the rocky cycle.

Change-Id: I6d26785b3aa1fc75fb0ad2d45684d93e9628f61b

.zuul.yaml

@@ -10,6 +10,7 @@
     required-projects:
       - openstack-infra/shade
       - openstack/keystoneauth
+      - openstack/python-openstacksdk
       - openstack/os-client-config
 
 - job:
@@ -24,6 +25,7 @@
     required-projects:
       - openstack-infra/shade
       - openstack/keystoneauth
+      - openstack/python-openstacksdk
       - openstack/os-client-config
 
 - project-template:
@@ -131,6 +133,7 @@
       stable/queens devstack.
     required-projects:
       - name: openstack/keystoneauth
+      - name: openstack/python-openstacksdk
       - name: openstack/os-client-config
     vars:
       tox_install_siblings: true

releasenotes/notes/openstacksdk-depend-7793cdbe75ab18cf.yaml

@@ -0,0 +1,15 @@
+---
+issues:
+  - |
+    The openstacksdk dependency lists ``>=0.9.19``, however the **ACTUAL**
+    lower-bound is ``0.11.2``, which is the version of openstacksdk released
+    with Queens. Since the dependency does not have an upper bound, installing
+    shade from pip will result in the correct thing.
+other:
+  - |
+    In preparation for being a compat layer during the Rocky timeframe, shade
+    now depends on openstacksdk and gets all of its dependencies as transitive
+    depends through openstacksdk. Subsequent shade releases will begin
+    replacing code inside of shade and will instead call the openstacksdk
+    copies of the relevant code. The shade backwards compat contract remains
+    in place and users should not notice any regressions.

requirements.txt

@@ -3,20 +3,5 @@
 # process, which may cause wedges in the gate later.
 pbr!=2.1.0,>=2.0.0 # Apache-2.0
 
-munch>=2.1.0 # MIT
-decorator>=3.4.0 # BSD
-jmespath>=0.9.0 # MIT
-jsonpatch>=1.16 # BSD
-ipaddress>=1.0.16;python_version<'3.3' # PSF
 os-client-config>=1.28.0 # Apache-2.0
-# These two are here to prevent issues with version pin mismatches from our
-# client library transitive depends.
-requestsexceptions>=1.2.0 # Apache-2.0
-six>=1.10.0 # MIT
-futures>=3.0.0;python_version=='2.7' or python_version=='2.6' # BSD
-iso8601>=0.1.11 # MIT
-
-keystoneauth1>=3.2.0 # Apache-2.0
-netifaces>=0.10.4 # MIT
-
-dogpile.cache>=0.6.2 # BSD
+openstacksdk>=0.9.19 # Apache-2.0