[tidy] Fix linting issues in notify_comment_error.test.cjs

[dsyme]

Summary

Fixed JavaScript linting issues in the test file notify_comment_error.test.cjs that were preventing the codebase from passing linting checks.

Changes Made

Fixed Duplicate Object Keys

• Issue: Multiple test cases had duplicate body: keys in expect.objectContaining() calls, which is invalid JavaScript syntax
• Solution: Converted to use expect.stringMatching() with regex patterns to match multiple string patterns in a single assertion

Specific Changes

• Updated 7 test assertions from duplicate keys to regex patterns:
  • Success message: ✅.*completed successfully
  • Failure message: ❌.*failed.*wasn't able to produce a result
  • Cancelled message: 🚫.*was cancelled
  • Timeout message: ⏱️.*timed out
  • Skipped message: ⏭️.*was skipped
  • GraphQL success: ✅.*completed successfully
  • GraphQL failure: ❌.*failed

Validation

• ✅ make fmt - All code properly formatted
• ✅ make lint - All linting checks passing
• ✅ make test - All tests passing (including the modified test file)
• ✅ make recompile - All workflows recompiled successfully

Before & After

Before (Invalid - Duplicate Keys):

expect.objectContaining({
  owner: "testowner",
  repo: "testrepo",
  comment_id: 123456,
  body: expect.stringContaining("✅"),
  body: expect.stringContaining("completed successfully"), // Duplicate key!
})

After (Valid - Regex Pattern):

expect.objectContaining({
  owner: "testowner",
  repo: "testrepo",
  comment_id: 123456,
  body: expect.stringMatching(/✅.*completed successfully/s),
})

Impact

This change ensures the codebase passes all linting checks and maintains code quality standards. The test functionality remains identical - the assertions still verify the same behavior, just with cleaner syntax.

AI generated by Tidy