Suppress consider-using-with on return statements

[DudeNr33]

• 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.

Type of Changes

	Type
✓	🐛 Bug fix

Description

As discussed in #4748 the consider-using-with check should be suppressed on return statements.

The new proposal for consider-using-context-manager is not included in this MR. I think we should discuss the use cases where this message should - and especially should not - trigger before starting the implementation.

Closes #4748

[coveralls]

Pull Request Test Coverage Report for Build 1133028673

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

---

Totals
Change from base Build 1132425686:	0.004%
Covered Lines:	13393
Relevant Lines:	14445

---

💛 - Coveralls

[Pierre-Sassoulas]

I agree with you, let's first remove the "false positive" before adding another check.