pylint: ignore possibly/used-before-assignment as it is prone to FP

It does no control flow analysis, and upgrading to pylint 3.2.0 produced
many incorrect warnings.

Also ignore contextmanager-generator-missing-cleanup for now. It has FP
when there is no code after a yield (and thus no cleanup needs to be
handled), which is what we do. Currently under discussion upstream:
pylint-dev/pylint#9625

(cherry picked from commit e343590)

.pylintrc

@@ -17,6 +17,7 @@ disable=
     cell-var-from-loop,
     consider-using-f-string,
     consider-using-with,
+    contextmanager-generator-missing-cleanup,
     cyclic-import,
     deprecated-decorator,
     duplicate-code,
@@ -47,6 +48,7 @@ disable=
     not-an-iterable,
     not-callable,
     pointless-string-statement,
+    possibly-used-before-assignment,
     protected-access,
     raise-missing-from,
     redeclared-assigned-name,
@@ -75,6 +77,7 @@ disable=
     unsubscriptable-object,
     unused-argument,
     unused-variable,
+    used-before-assignment,
     useless-super-delegation,
     wrong-import-order,
     wrong-import-position,