False positive builtin name detection in exception handler body

Describe the bug Names in exception handler body could be incorrectly determined as builtin features used.

To Reproduce

File:

for file in ['foo']:
    try:
        1 / 0
    except ZeroDivisionError:
        print(file)

Result:

Detecting python files..
Analyzing using 8 processes..
2.0, !3      test.py
  print(expr) requires 2.0, 3.0
  L5 C14: 'file' member requires 2.0, !3

Minimum required versions: 2.0
Incompatible versions:     3

Expected behavior

Should not detect file as Python 2 builtin file member.

Environment

• Vermin version: 1.1.1

Additional context This is due to commit bd9ded9 for addressing #45. To match the current detection heuristics (outside of exception handlers), we should not look for builtin exceptions in the body attribute of an ExceptHandler node, but only look for them inside the type attribute.

It would also be better to recognize file as a user-defined name in this case. There are many kinds for syntactic structures which create new variables (bind names) in Python:

• Assignment (regular assignment, augmented assignment, annotated assignment, walrus)
• import statements
• Function and class definitions (the function/class name is a variable in the containing scope)
• Function argument list (an argument is a local variable of the function)
• for loops and comprehensions
• with ... as ...
• except ... as ...
• And pattern matching in 3.10 may also bind names

[gousaiyang]

It’s great!

[netromdk]

Great. Then I think 4a6a94e is ready. Thanks again.