Make LeakCanary more strict

[rjrjr]

trafficstars

Reported by @pyricau: At the moment we are only checking for leaks after the activity is destroyed, which means there is a huge window we're missing. We should check before that as well:

@get:Rule val rules = RuleChain.outerRule(DetectLeaksAfterTestSuccess()).around(scenarioRule).around(DetectLeaksAfterTestSuccess())!!

[pyricau]

This makes we wonder if there's a clever API we can have that says "do this both inside and outside this chain of rules"