Fix unstable trailing comment on a parenthesized arrow chain - #19930

Description

js/arrows/arrow-chain-with-trailing-comments.js is listed in failed-format-tests.js as unstable. This fixes it and removes the entry.

// Input
x2 = (a) => ((b) => {
  c();
} /* ! */ // K
)

// Prettier stable (first format)
x2 = (a) => (b) => {
  c();
} /* ! */; // K

// Prettier stable (second format)
x2 = (a) => (b) => {
  c();
}; /* ! */ // K

// Prettier main
x2 = (a) => (b) => {
  c();
}; /* ! */ // K

The parentheses around the inner arrow are redundant, so they are dropped. That leaves the comment sitting between } and the statement's semicolon, and the next format attaches it to the ExpressionStatement rather than to the arrow it was written against, so it prints on the other side of the semicolon.

handleParenthesizedExpressionTrailingComment already handles the same situation for a nested assignment (a = (b = c /* comment */)) by attaching the comment to the statement immediately instead of leaving it for the next format to move. This extends that to a chain that passes through arrow bodies, so the first format produces what the second one would.

Checklist

• I’ve added tests to confirm my change works.
• (If changing the API or CLI) I’ve documented the changes I’ve made (in the docs/ directory).
• (If the change is user-facing) I’ve added my changes to changelog_unreleased/*/XXXX.md file following changelog_unreleased/TEMPLATE.md.
• I’ve read the contributing guidelines.
• I did not use AI to generate this PR.
• (If the above is not checked) I have reviewed the AI-generated content before submitting.

No new test is added because the fixture already exists; it was listed as unstable rather than passing, and that entry is now removed. Verified with the full tests/format/js, typescript, jsx and flow suites: the set of failing tests is identical to main on my machine, with the arrows snapshot updated to the second-pass output. I used AI assistance and reviewed everything before submitting.