events: refactored emit to improve performance

[KunalKumar-1]

These changes improve the overall efficiency and maintainability of the emit method

• Refactored error handling logic for clarity and efficiency
• Streamlined error inspection and stringification process
• Enhanced stack trace handling with minimal performance overhead
• Simplified listener iteration and result handling in emit method

Fixes: #53056

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.20%. Comparing base (08eeddf) to head (79a8f78).
Report is 380 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #56741      +/-   ##
==========================================
- Coverage   89.21%   89.20%   -0.01%     
==========================================
  Files         662      662              
  Lines      191968   191958      -10     
  Branches    36955    36952       -3     
==========================================
- Hits       171269   171242      -27     
- Misses      13535    13552      +17     
  Partials     7164     7164              

Files with missing lines	Coverage Δ
lib/events.js	99.58% <100.00%> (-0.17%)	⬇️

... and 42 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mertcanaltin]

hello , I did a node version benchmark in my local, is this healthy? @anonrig @targos

Be aware that when doing many comparisons the risk of a false-positive result increases.
In this case, there are 88 comparisons, you can thus expect the following amount of false-positive results:
4.40 false positives, when considering a 5% risk acceptance *, **, ***,
0.88 false positives, when considering a 1% risk acceptance **, ***,
0.09 false positives, when considering a 0.1% risk acceptance ***

string_decoder/string-decoder-create.js n=25000000 encoding='utf-8' at *** (improvement)

string_decoder/string-decoder.js n=2500000 chunkLen=1024 inLen=32 encoding='ascii' * (improvement)

string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=1024 encoding='ascii' * (improvement)

string_decoder/string-decoder.js n=2500000 chunkLen=16 inLen=32 encoding='ascii' * (improvement)

all result: https://ctxt.io/2/AAB4UTAXEQ

[KunalKumar-1]

why running String-decoder benchmark ?