Pin astroid due to false no-name-in-module and no-member errors (…

…ansible#773)

Pin `astroid` due to false `no-name-in-module` and `no-member` errors

astroid >= 2.9.1, =< 2.9.3 (a pylint dependency) has a bug causing the reports of false-positive no-name-in-module and no-member rule violations.
This patch pins the respective transitive dependency to the last known good version of 2.9.0 as a temporary workaround.
It should be reverted as soon as the underlying upstream bug is fixed.
Ref: pylint-dev/pylint#5131
Related: ansible#772

Reviewed-by: Sviatoslav Sydorenko <webknjaz+github/profile@redhat.com>
Reviewed-by: None <None>

tox.ini

@@ -74,9 +74,18 @@ commands =
 deps =
   {[testenv]deps}
   -r{toxinidir}/docs/requirements.in
+  # direct dependencies
   pylint
   pylint-pytest < 1.1.0
 
+  # indirect dependencies
+  # astroid is a transitive dep for pylint, > 2.9.0 introduces false no-name-in-module and no-member errors
+  # attempt to remove this when astroid 2.9.4 or later is released
+  # related: https://github.com/PyCQA/pylint/issues/5131
+  # related: https://github.com/ansible/ansible-navigator/issues/772
+  astroid == 2.9.0
+
+
 [testenv:lint-vetting]
 description =
   Vetting newer quality standards under `{basepython}` ({envpython})