Async try...catch is not properly handled and throws an error where it shouldn't

This perfectly fine jest test fails with `jest-plugin-must-assert`:

```ts
describe("Async Try Catch", () => {
it('should work', async () => {
try {
await Promise.reject('whoop')
} catch (e) {
console.log('error catched')
}
expect(true).toBe(true)
})
})
```

The test works fine when the promise rejection is delayed with `setTimeout`:

```ts

describe("Async Try Catch 2", () => {
it('should work', async () => {
try {
await new Promise((_, reject) => {
setTimeout(() => reject('whoop'))
})
} catch (e) {
console.log('error catched')
}
expect(true).toBe(true)
})
})
```

This was especially hard to debug because I was initially using mockRejectedValue(...) in a jest test.

Start by reproducing the Jest example with an immediately rejected Promise and compare it with the setTimeout rejection case. The issue does not name a source file or test path, so locate the plugin's async assertion handling and add coverage for both examples. Done means a caught immediate rejection does not produce a spurious error while the assertion still runs.

Written by the indexing model from the issue text.