feat(linter): implement no-promise-executor-return rule

[tt-a1i]

Summary

Implements ESLint's no-promise-executor-return rule which disallows returning values from Promise executor functions.

The return value of a Promise executor is ignored, so returning a value is likely a mistake. This rule detects:

• Implicit returns from arrow function expression bodies (new Promise(r => r(1)))
• Explicit return statements with values (return 1, return resolve(1))
• Returns inside control flow (if, switch, loops, try-catch, etc.)

Configuration

• allowVoid (default: false): When true, allows return void expr pattern (both explicit and implicit returns)

Design Notes

This rule only checks executors passed directly as arrow/function expressions. It does not track references like new Promise(executor) where executor is defined elsewhere — this is an intentional design choice consistent with ESLint's implementation.

Test Plan

• Added 12 pass cases (empty return, no return, nested functions, allowVoid, non-Promise)
• Added 16 fail cases (implicit return, explicit return, control flow, return resolve/reject)
• cargo test -p oxc_linter no_promise_executor_return passes
• cargo clippy -p oxc_linter passes

Closes #7790

[codspeed-hq]

CodSpeed Performance Report

Merging #16779 will not alter performance

_{Comparing tt-a1i:feat/linter-no-promise-executor-return (bd642bf) with main (fbcb49a)¹}

Summary

✅ 4 untouched
⏩ 41 skipped²

Footnotes

1. No successful run was found on main (2124d03) during the generation of this report, so fbcb49a was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩