feat(biome_js_analyse): added new option to rule to ignore unused function parameters

[vladimir-ivanov]

Summary

Added ignoreRestSiblings option to noUnusedFunctionParameters rule to ignore unused function parameters that are siblings of the rest parameter.
Default is false, which means that unused function parameters that are siblings of the rest parameter will be reported.

Example

{
  "rules": {
    "noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]
  }
}

closes #5941

[codspeed-hq]

CodSpeed Performance Report

Merging #6405 will not alter performance

_{Comparing vladimir-ivanov:feat/noUnusedFunctionParameter-add-ignoreRestSiblingss-option (92011a4) with main (ef2421d)}

Summary

✅ 114 untouched benchmarks

[vladimir-ivanov]

review please :-)

[ematipico]

Blocking to avoid accidental merges, since it's a minor

[changeset-bot]

🦋 Changeset detected

Latest commit: 92011a4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 14 packages

Name	Type
@biomejs/biome	Minor
@biomejs/cli-win32-x64	Minor
@biomejs/cli-win32-arm64	Minor
@biomejs/cli-darwin-x64	Minor
@biomejs/cli-darwin-arm64	Minor
@biomejs/cli-linux-x64	Minor
@biomejs/cli-linux-arm64	Minor
@biomejs/cli-linux-x64-musl	Minor
@biomejs/cli-linux-arm64-musl	Minor
@biomejs/wasm-web	Minor
@biomejs/wasm-bundler	Minor
@biomejs/wasm-nodejs	Minor
@biomejs/backend-jsonrpc	Patch
@biomejs/js-api	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vladimir-ivanov]

are we merging this anytime soon please? @ematipico

[arendjr]

@vladimir-ivanov Since it's targeting the next minor, we can't merge to main yet, since we may still create patch releases from there. If you're eager to see it merged you can also rebase on top of next, where we can merge it anytime.

In the #maintainers channel on Discord there was also a discussion around branching strategy the other day, with ideas that might allow us to open up main sooner, although we could use some help on updating the docs and maybe CI if we were to make that change. Feel free to chip in if you're interested in that ;)

[vladimir-ivanov]

@vladimir-ivanov Since it's targeting the next minor, we can't merge to main yet, since we may still create patch releases from there. If you're eager to see it merged you can also rebase on top of next, where we can merge it anytime.

In the #maintainers channel on Discord there was also a discussion around branching strategy the other day, with ideas that might allow us to open up main sooner, although we could use some help on updating the docs and maybe CI if we were to make that change. Feel free to chip in if you're interested in that ;)

leaving to someone else to merge once it is allowed to go in then, thank you :-)

[vladimir-ivanov]

@ematipico @dyc3 is this good to go now please?

[dyc3]

Under the contribution guide changes in #6664, this would need to go onto next instead of main, but we don't have that set up yet. This can move forward when that is resolved.

[ematipico]

It can go to main, because we already have minor changes. Good to go!