Scans initiated by tests failed by timeout get disrupted

[wawaqa]

If a test fails by timeout, it leaves a scan in the app. Once the scan start, the repeater is already removed, therefore the scan finds no EPs and gets discrupted.
Steps to reproduce:

1. Set low Jest timeout (e.g. 10 secs)
2. Run a test which starts a scan inside and then fails by timeout.
3. Observe the scan.

Actual: scan gets disrupted since by the time it starts the repeater is already removed and therefore no EPs are found.
Expected: we should think about a more graceful way to handle such a situation (stop a scan inside runner.clear() used in afterAll hook?)

There may be 2 problems here:

• the reason for the scan getting disrupted may not look obvious for a user
• if we collect statistics/investigate why scans get disrupted, such scans may cause some kind of a noise.