[Feature]: Use browser in OneTimeSetUp and OneTimeTearDown

🚀 Feature Request

Very often we need to make some actions during OneTimeSetUp and make some cleaning in OneTimeTearDown and we need to open the same browser that we have.
Now it is possible via work-around for OneTimeTearDown, but absently not possible for OneTimeSetUp.

Example

[TestFixture]
public class MyTests : PlaywrightTest
{
    [OneTimeSetUp]
    public async Task OneTimeSetUp()
    {
        // Access to fixture-level browser instances
        var page = await FixtureBrowser.NewPageAsync();
        
        // Perform global setup
        
    }
}

Motivation

Now we need to duplicate the logic to run browser to some place to be able to run playwright in OneTimeSetUp, which can cause a lot of issues or just do not use adaptor at all.

Start by tracing the test adapter's lifecycle around OneTimeSetUp, OneTimeTearDown, and fixture-level browser instances. Determine how the existing teardown workaround starts or exposes the browser, then define the equivalent setup path; done means both callbacks can access the same browser without duplicated launch logic, with coverage for the lifecycle behavior.