[Ilya Trapashko (itrapashko)]

Fixes #1944

The wrapper now forwards only the parameters that were actually passed, as sendRequest does. [any?] is used instead of any[] so that the spread matches the (method) and (method, params) overloads of ProtocolConnection.

A notification with an explicit undefined parameter (e.g. NotificationType<void>) is still sent as [null].

[Copilot]

🟢 Approval recommended

No active review issues remain for the change preserving omitted notification parameters.

No open issues 🎉

What changed in this PR

Fixes #1944 by preserving omitted notification parameters in the server connection wrapper, preventing parameterless notifications from being sent with params: [null].

Changes:

• Forward only supplied notification arguments, matching the sendRequest wrapper.
• Preserve existing behavior for explicitly passed undefined.
• Add a regression test confirming that parameterless notifications deliver zero arguments.

File	Description
server/​src/​node/​test/​connection.test.ts	Adds regression coverage for notifications without parameters.
server/​src/​common/​server.ts	Uses an optional rest tuple to preserve the number of supplied arguments.

_{Review effort: Balanced}