Use fullName in TestResult

[connectdotz]

Motivation

The TestResult.name was from the source block, which has led to a few problems during debugging as we used the name as the --testNamePattern:

1. it only has lexical string, i.e. no runtime translation like template-literal, therefore not able to debug with --testNamePattern.
   • we should used the info from assertions, not source block
2. it doesn't have the hierarchical context, i.e. describe blocks, so if the file has multiple tests with the same name under different describe blocks, they will all be executed
   • solution: use assertions.fullName resolved this, now the debug can be precise

Implementation

• This PR mainly modified the logic of how we extract TestResult.name.
  • Optionally, capture all the relevant names in a new property names in case it is needed in the future.
• upgrade jest

Notes

• added some test with test.each so we can make sure it worked for us and our users. However, these tests will need the new jest to work properly in vscode, so you will need to build the extension with this PR in order to test in vscode.

---

fixes #627
fixes #620 (particularly this comment)

[connectdotz]

ping @seanpoulter @stephtr hey, will any of you have some cycle to review this PR?

[connectdotz]

@seanpoulter @stephtr, looks like you guys are swapped, then what do you guys think we could do? Just merge in or you have other suggestions?

[connectdotz]

hmmm... I didn't hear anything from anybody, hopefully, everybody is doing all right and just busy... In the spirit of helping our users, let's merge it in alpha so we can fix and release v4 soon.