test: fixate linters version strictly

Any new linter release, including bugfix ones, may result in failing CI.
Since tarantool-python CI is included in several integration pipelines,
such things may block work on repos like tarantool/tarantool and
tarantool/luajit. On the other hand, if CI will start to fail due to a
new linter release, it is unlikely that something user-critical will be
discovered. So for now let's stick to the following approach: one will
bump linters manually from time to time and fix/disable emerging issues.

Author: DifferentialOrange

requirements-test.txt

@@ -1,8 +1,10 @@
 git+https://github.com/baztian/dbapi-compliance.git@ea7cb1b4#egg=dbapi-compliance
 pyyaml==6.0
 importlib-metadata >= 1.0 ; python_version < '3.8'
-pylint ~= 3.0 ; python_version >= '3.8'
-pylint ~= 2.13 ; python_version < '3.8'
-flake8 ~= 6.1 ; python_version >= '3.8'
-flake8 ~= 5.0 ; python_version < '3.8'
-codespell ~= 2.2
+pylint == 3.3.0 ; python_version >= '3.9'
+pylint == 3.2.7 ; python_version == '3.8'
+pylint == 2.17.7 ; python_version == '3.7'
+flake8 == 6.1.0 ; python_version >= '3.8'
+flake8 == 5.0.4 ; python_version < '3.8'
+codespell == 2.3.0 ; python_version >= '3.8'
+codespell == 2.2.5 ; python_version < '3.8'