Remove misplaced pure annotations

[TheAlexLichter]

This PR removes invalid /*#__PURE__*/ comments from private helper function.

These annotations only apply to call/new expressions, so they are ignored in this position and can produce INVALID_ANNOTATION warnings in downstream bundlers.

Resolves #55286

See also rolldown/rolldown#9496

[dotnet-policy-service]

Thanks for your PR, @TheAlexLichter. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[Copilot]

Pull request overview

Removes misplaced /*#__PURE__*/ annotations from private helper function declarations in the SignalR TypeScript client to avoid downstream bundler INVALID_ANNOTATION warnings, without changing helper behavior.

Changes:

• Removed /*#__PURE__*/ annotations and the associated eslint suppression from getOsName and getRuntimeVersion helper declarations.
• Kept the helper implementations and call sites unchanged.

[baevm]

there is also a related issue: #55286

[BrennanConroy]

Some context #55496 (comment)

Although, re-reading the webpack docs it looks like #__PURE__ is meant for the caller of the function not the function itself 😲

Looks like if we update webpack to 5.107.0+ we can use the #__NO_SIDE_EFFECTS attribute https://webpack.js.org/guides/tree-shaking/#mark-a-function-declaration-as-side-effect-free