fix(js_formatter): fix some random indention inconsistencies

[faultyserver]

Summary

Just fixing two little issues I found running Biome on a large codebase. Commenting inline on each fix below.

Test Plan

Managed to remove another diff snapshot :)

[netlify]

✅ Deploy Preview for biomejs canceled.

Name	Link
🔨 Latest commit	0d6fed9
🔍 Latest deploy log	https://app.netlify.com/sites/biomejs/deploys/6578c7852f8c2900086daac2

[faultyserver]

This whole diff is a little bit weird, but this just moves the leading comment inside of the signature formatting, ensuring that it picks up the potential indention that's applied below (line +590).

It fixes this:

foo(
  () =>
  // a comment
    () => {}
)

which should actually be formatted to

foo(
  () =>
    // a comment
    () => {}
)

where the leading comment lines up with the following parens.

[faultyserver]

When a binary expression is part of the call arguments, its grand parent is JsCallArgumentList, not just JsCallExpression. These intermediary nodes make it kind of hard to compare directly to prettier, but come up consistently (other places also have to check like JsParameterList instead of JsFunctionDeclaration, for example).

Adding this here means that binaries are formatted consistently whether they're the receiver or an argument to a call expression:

foo(
  someCondition === true ||
  anotherCondition === false
);

should actually indent the right hand side, but wasn't because the grandparent is JsCallArgumentList, but this was only checking for JsCallExpression directly. Now it matches Prettier as:

foo(
  someCondition === true ||
    anotherCondition === false
);