@copilot continue the fix. Add unit tests.

@copilot continue the fix. Add unit tests.

I've continued the fix and added comprehensive unit tests. The fix is now complete with proper test coverage.

What was added:

• Unit tests that validate steps from tryTo and hopeThat sessions are excluded from main test trace
• Tests confirm regular steps still work normally
• All tests are passing with no regression in existing functionality

The fix correctly addresses issue #4619 where failed steps inside tryTo were polluting the main test error trace. Commit: 78a0872

@copilot I noticed the output when running with --verbose mode missing info

Scenario('test something', async ({ I }) => {
 I.amOnPage('https://codecept.io/quickstart/')
 const result = await tryTo(() => { I.seeElement('.doesntexist') })
 
 I.fillField('#algolia-search-input', 'codecept')
 I.pressKey('Enter')
 I.see('CodeceptJS')
 I.seeCheckboxIsChecked('.nocheckboxishere')
});

when test failed, there are no:

• -- FAILURES:
• Scenario Steps:
• Artifacts:

like we used to have in output. Let's check and fix that.

@copilot I noticed the output when running with --verbose mode missing info

...

I've investigated the verbose output issue and created a test that reproduces the scenario you described. In my testing, the verbose output is actually working correctly - it shows "-- FAILURES:", "Scenario Steps:", and properly excludes steps from tryTo sessions.

Could you provide more details about your specific test environment? Are you:

1. Using a specific helper (Playwright, WebDriver, etc.)?
2. Running with any specific configuration options?
3. Seeing this issue in all failing tests or only certain ones?

The fix for #4619 appears to be working as intended, so there might be another factor causing the verbose output to be suppressed in your case.