Revisiting requiring explicit `self.` when passing a method as an escaping closure

[hartbit (David Hart)]

@nonsensery

Yes – here is another type of implicit capture that I’ve seen:

I had a proposal to also resolve this. Its similar to yours: https://github.com/hartbit/swift-evolution/blob/improving-capturing-semantics-of-local-functions/proposals/XXXX-improve-capture-semantics-of-local-functions.md