fix: display stack trace and code frame for findBy error

[matthieugicquel]

Summary

This fixes #547 with a solution more or less copied from this file in dom-testing-library.

A useful stack trace and codeframe are now shown for findBy failures.

Test plan

Note that to get the correct codeframe, the repo running the test must be another that uses this repo as a package, this won't work in the internal tests.

I didn't add any test because I'm not sure assertions on the stack trace make sense...

Contrary to the issue above, the stacktrace was already working with waitFor for me, so while it should improve the situation for waitFor calls too, I can't be sure of it.

Improving the stack trace more

The stack trace still has 2 useless/internal lines, but I suspect to get rid of these, we must:

• either filter the stack trace string manually
• or rewrite all the findBy*** helpers to capture the error here

I figured I would open this PR before digging more, since the most important part works :)

[thymikee]

Thanks!