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: I817e5112eb57df2e6192d3cfa681b7768832c77a
(cherry picked from commit 184161dc01)

.zuul.yaml

@@ -32,7 +32,6 @@
       - publish-openstack-docs-pti
       - periodic-stable-jobs
       - release-notes-jobs-python3
-      - openstack-lower-constraints-jobs
     check:
       jobs:
         - grenade-ceilometer

lower-constraints.txt

@@ -1,47 +0,0 @@
-cachetools==2.1.0
-cotyledon==1.3.0
-coverage==4.0
-cryptography==3.2.0
-fixtures==3.0.0
-futurist==1.8.0
-gabbi==1.30.0
-gnocchiclient==7.0.0
-jsonpath-rw-ext==1.1.3
-keystoneauth1==3.18.0
-lxml==4.5.1
-msgpack==0.5.2
-os-win==3.0.0
-oslo.cache==1.26.0
-oslo.concurrency==3.26.0
-oslo.config==6.0.0
-oslo.i18n==3.15.3
-oslo.log==3.36.0
-oslo.messaging==8.0.0
-oslo.privsep==1.32.0
-oslo.reports==1.18.0
-oslo.rootwrap==2.0.0
-oslo.utils==4.5.0
-oslo.vmware==2.17.0
-oslotest==3.2.0
-pbr==2.0.0
-pyOpenSSL==17.1.0
-pysnmp==4.2.3
-python-cinderclient==3.3.0
-python-glanceclient==2.8.0
-python-keystoneclient==3.18.0
-python-monascaclient==1.12.0
-python-neutronclient==6.7.0
-python-novaclient==9.1.0
-python-swiftclient==3.2.0
-python-zaqarclient==1.3.0
-python-subunit==1.4.0
-PyYAML==5.1
-requests==2.14.2
-requests-aws==0.1.4
-six==1.10.0
-stestr==2.0.0
-stevedore==3.0.0
-tenacity==6.3.1
-testresources==2.0.1
-testscenarios==0.4
-testtools==2.2.0

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

@@ -85,9 +85,3 @@ extension =
     C301 = checks:no_log_warn
     C302 = checks:no_os_popen
 paths = ./ceilometer/hacking
-
-[testenv:lower-constraints]
-deps =
-  -c{toxinidir}/lower-constraints.txt
-  -r{toxinidir}/test-requirements.txt
-  -r{toxinidir}/requirements.txt