[Feat] Allow `return void` for rules `noSetterReturn` `noConstructorReturn` `noVoidTypeReturn`

[Conaclos]

Description

Keywords

linter, rules, return, void, noSetterReturn, noConstructorReturn, noVoidTypeReturn

Summary

This issue is open for gathering opinions and interest about the support
of return void in the following rules:

• noConstructorReturn (feat(rome_js_analyze): noConstructorReturn #3805)
• noSetterReturn (feat(rome_js_analyze): noSetterReturn #3783)
• noVoidTypeReturn (feat(rome_js_analyze): noVoidTypeReturn #3806)

Currently, these rules disallow any return statement with an argument.
Only returning without argument is allowed.

The rule could be relaxed for supporting return void.

class A {
  constructor() {
    this._prop = 0;
    return void 0;
  }

  set prop(prop: number) {
    this._prop = prop;
    return void 0;
  }

  function f(): void {
    return 0;
  }
}

Note: currently, ESLint does not support return void.

[github-actions]

👋 @rome/staff please triage this issue by adding one of the following labels: S-Bug: confirmed, S-Planned , S-Wishlist or umbrella