Drop lower-constraints.txt and its testing

As discussed in TC PTG[1] and TC resolution[2], we are
dropping the lower-constraints.txt file and its testing.
We will keep lower bounds in the requirements.txt file but
with a note that these are not tested lower bounds and we
try our best to keep them updated.

[1] https://etherpad.opendev.org/p/tc-zed-ptg#L326
[2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal

Change-Id: I73718d9f52d11b9a17ab49468743d5237179ada5

.zuul.yaml

@@ -2,7 +2,6 @@
     templates:
       - check-requirements
       - lib-forward-testing-python3
-      - openstack-lower-constraints-jobs
       - openstack-python3-ussuri-jobs
       - openstacksdk-functional-tips
       - openstacksdk-tox-tips

lower-constraints.txt

@@ -1,54 +0,0 @@
-appdirs==1.4.3
-Babel==2.8.0
-bandit==1.1.0
-betamax==0.7.0
-certifi==2018.1.18
-coverage==4.0
-debtcollector==1.19.0
-dulwich==0.19.0
-entrypoints==0.3
-extras==1.0.0
-fixtures==3.0.0
-future==0.16.0
-gitdb2==2.0.3
-GitPython==2.1.8
-iso8601==0.1.11
-linecache2==1.0.0
-lxml==4.2.0
-mock==2.0.0
-monotonic==1.4
-mox3==0.25.0
-netaddr==0.7.19
-netifaces==0.10.6
-oauthlib==0.6.2
-os-client-config==1.29.0
-os-service-types==1.2.0
-oslo.config==5.2.0
-oslo.i18n==3.20.0
-oslo.utils==3.33.0
-oslotest==3.2.0
-pbr==2.0.0
-pep257==0.7.0
-pykerberos==1.2.1
-pyparsing==2.2.0
-python-mimeparse==1.6.0
-python-subunit==1.2.0
-pytz==2018.3
-PyYAML==3.12
-reno==3.1.0
-requests==2.14.2
-requests-kerberos==0.8.0
-requests-mock==1.2.0
-requestsexceptions==1.4.0
-rfc3986==1.1.0
-six==1.10.0
-smmap2==2.0.3
-stestr==1.0.0
-stevedore==1.20.0
-testrepository==0.0.20
-testresources==2.0.0
-testtools==2.2.0
-traceback2==1.4.0
-unittest2==1.1.0
-urllib3==1.22
-wrapt==1.10.11

requirements.txt

@@ -1,3 +1,7 @@
+# Requirements lower bounds listed here are our best effort to keep them up to
+# date but we do not test them so no guarantee of having them all correct. If
+# you find any incorrect lower bounds, let us know or propose a fix.
+
 # The order of packages is significant, because pip processes them in the order
 # of appearance. Changing the order has an impact on the overall integration
 # process, which may cause wedges in the gate later.

tox.ini

@@ -101,9 +101,3 @@ commands = sphinx-build -a -E -W -d releasenotes/build/doctrees -b html releasen
 extension =
     K333 = checks:check_oslo_namespace_imports
 paths = ./keystoneauth1/hacking
-
-[testenv:lower-constraints]
-deps =
-  -c{toxinidir}/lower-constraints.txt
-  -r{toxinidir}/test-requirements.txt
-  -r{toxinidir}/requirements.txt