Fix false-positive consider-using-with for ternary conditionals in with items

[DudeNr33]

Steps

• Add a ChangeLog entry describing what your PR does.
• If it's a new feature or an important bug fix, add a What's New entry in
  doc/whatsnew/<current release.rst>.
• Write a good description on what the PR does.

Description

For details see #4676 - things like open calls inside ternary conditionals used in a with were incorrectly flagged with the consider-using-with, because the check if this call happens inside the items of a with only looked at the first parent node.
This is now expanded to check all parents until we reach the enclosing frame.

I also ran pylint over a few other codebases (black, requests, pip, twine) and (luckily 😁) found no new edge cases.
But I somehow have a feeling that this won't stay the last fix of false-positives for consider-using-with...

Type of Changes

	Type
✓	🐛 Bug fix

Related Issue

Closes #4676

[coveralls]

Coverage increased (+0.006%) to 92.051% when pulling 0708099 on DudeNr33:fix-4676-false-positive-r1732 into 0f8212f on PyCQA:main.

[Pierre-Sassoulas]

There could be other use case but I think this is converging fast 😉 Thanks for fixing this so fast, much appreciated !