feat(testing): add context to beforeEach and afterEach hooks

[Mr-Duda]

Fixes #6189

This allows the beforeEach and afterEach methods to use the data provided in each test context object.

I wanna build a small decorator based test framework on top of deno testing. The usecase is the following:

• before each test /path/TestCaseTest/testFileNotExistsThrowsError/{in,out} folders are created if needed
• it
  • reads some files from .../testFileNotExistsThrowsError/in
  • creates some files in .../testFileNotExistsThrowsError/out using a custom context wrapper
• after each test the .../testFileNotExistsThrowsError/out is cleaned up to prevent unwanted outputs

@TestSuite
class TestCaseTest extends TestCase {

    @Test
    public testFileNotExistsThrowsError(context: iTestContext) {
        // Read files...
        context.createFile("./dummy.txt", "dummy")
        return this.assertThrows(() => this.assertFileNotExists("./dummy.txt", context))
    }
}

Currently the beforeEach and afterEach don't have access to the test name and it's somehow difficult to get this information.
The test source file would also be needed at some point and i would't use __filename since it's also provided in the test context.

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.57%. Comparing base (93e0cd6) to head (7ca8dfd).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6201      +/-   ##
==========================================
+ Coverage   96.56%   96.57%   +0.01%     
==========================================
  Files         532      532              
  Lines       40819    40819              
  Branches     6111     6111              
==========================================
+ Hits        39416    39421       +5     
+ Misses       1360     1356       -4     
+ Partials       43       42       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[kt3k]

Why not just use native Deno.test() and t.step()? These APIs should be more flexible than @std/testing/bdd and they should be more suitable for building testing framework on top of

[Mr-Duda]

I shitched to using the Deno namespace and it works fine.