Cap jsonschema 3.2.0 as the minimal version

Previous versions of jsonschema (<3.2.0) doesn't support python 3.8 [1].
Python 3.8 is part of the victoria supported runtimes [2] so we now force
to use jsonschema version 3.2.0 to avoid issues, remove ambiguity and ensure
that everything works with python 3 in general.

This patch also advances tempest to 25.0.0 and oslo.concurrency to 3.26.0
for proper python3 support.

[1] https://github.com/Julian/jsonschema/pull/627
[2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria

Change-Id: Iaf5ff97322ff6f18a3693dead20ec8f6fe7561ad

lower-constraints.txt

@@ -20,7 +20,7 @@ iso8601==0.1.11
 jmespath==0.9.0
 jsonpatch==1.16
 jsonpointer==1.13
-jsonschema==2.6.0
+jsonschema==3.2.0
 keystoneauth1==3.4.0
 linecache2==1.0.0
 monotonic==0.6
@@ -33,7 +33,7 @@ openstacksdk==0.11.2
 os-client-config==1.28.0
 os-service-types==1.2.0
 osc-lib==1.8.0
-oslo.concurrency==3.25.0
+oslo.concurrency==3.26.0
 oslo.config==5.2.0
 oslo.context==2.19.2
 oslo.i18n==3.15.3
@@ -61,7 +61,7 @@ requestsexceptions==1.2.0
 rfc3986==0.3.1
 simplejson==3.5.1
 stevedore==1.20.0
-tempest==17.1.0
+tempest==25.0.0
 stestr==2.0.0
 testtools==2.2.0
 traceback2==1.4.0

requirements.txt

@@ -2,7 +2,7 @@
 # of appearance. Changing the order has an impact on the overall integration
 # process, which may cause wedges in the gate later.
 cliff!=2.9.0,>=2.8.0 # Apache-2.0
-jsonschema>=2.6.0 # MIT
+jsonschema>=3.2.0 # MIT
 osc-lib>=1.8.0 # Apache-2.0
 oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
 oslo.utils>=3.33.0 # Apache-2.0

test-requirements.txt

@@ -10,4 +10,4 @@ python-subunit>=1.0.0 # Apache-2.0/BSD
 requests-mock>=1.2.0 # Apache-2.0
 stestr>=2.0.0 # Apache-2.0
 reno>=3.1.0 # Apache-2.0
-tempest>=17.1.0 # Apache-2.0
+tempest>=25.0.0 # Apache-2.0