fix: hook exit code

[kobenguyent]

Motivation/Description of the PR

• Description of this PR, which problem it solves
• Resolves After and AfterSuite hooks return exit code 0 on failure instead of 1, incorrectly indicating success #5057

Applicable helpers:

• Playwright
• Puppeteer
• WebDriver
• REST
• FileHelper
• Appium
• TestCafe

Applicable plugins:

• allure
• autoDelay
• autoLogin
• customLocator
• pauseOnFail
• coverage
• retryFailedStep
• screenshotOnFail
• selenoid
• stepByStepReport
• stepTimeout
• wdio
• subtitles

Type of change

• 🔥 Breaking changes
• 🚀 New functionality
• 🐛 Bug fix
• 🧹 Chore
• 📋 Documentation changes/updates
• ♨️ Hot fix
• 🔨 Markdown files fix - not related to source code
• 💅 Polish code

Checklist:

• Tests have been added
• Documentation has been added (Run npm run docs)
• Lint checking (Run npm run lint)
• Local tests are passed (Run npm test)

[Copilot]

Pull Request Overview

This PR fixes hook exit code handling by ensuring that error reporting is consistent across all hook types. The change ensures that suiteTestFailedHookError is called for 'after' and 'afterSuite' hooks when errors occur, which was previously missing for these hook types.

• Adds suiteTestFailedHookError calls for 'after' and 'afterSuite' hooks
• Restructures conditional blocks for better readability with proper bracing
• Maintains existing event emission behavior for each hook type

[Copilot]

[nitpick] Consider using a switch statement or array includes for better readability when checking multiple hook types, especially as this pattern is repeated throughout the function.

Suggested change

	if (hookName === 'before' || hookName === 'beforeSuite') {
	if (['before', 'beforeSuite'].includes(hookName)) {