Check py-version for async unnecessary-dunder-call

[DanielNoord]

• Write a good description on what the PR does.
• Create a news fragment with towncrier create <IssueNumber>.<type> which will be
  included in the changelog. <type> can be one of: new_check, removed_check, extension,
  false_positive, false_negative, bugfix, other, internal. If necessary you can write
  details or offer examples on how the new change is supposed to work.
• If you used multiple emails or multiple names when contributing, add your mails
  and preferred name in script/.contributors_aliases.json

Type of Changes

	Type
✓	🐛 Bug fix

Description

Closes #7529.

[coveralls]

Pull Request Test Coverage Report for Build 3165251258

• 6 of 6 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.001%) to 95.333%

---

Totals
Change from base Build 3164548731:	0.001%
Covered Lines:	17118
Relevant Lines:	17956

---

💛 - Coveralls

[Pierre-Sassoulas]

I think we should handle this generically by changing this datastructure (DUNDER_METHODS) to include the min version of the dunder method. Maybe:

DUNDER_METHODS = {
    "3.10": {
       "__aiter__": "Use iter built-in function",
       "__anext__": "Use next built-in function",
    }
    "default" : {
        "__index__": "Use index method",
        "__round__": "Use round built-in function",
        ...
    }
}

[Pierre-Sassoulas]

Thank you for the fix !

[Pierre-Sassoulas]

Clever 👍