browser: forward remaining log arguments to write in asObject mode

[SnowingFox]

Fixes #2244

Problem

When a custom browser.write is used (which forces asObject mode), extra arguments passed to the log methods never reach the write function:

const logger = pino({ browser: { write: (logObj, ...logParams) => { /* ... */ } } })
logger.debug('bla', { di: 'da' })

Here { di: 'da' } is silently dropped: logParams is always empty because asObject() only returns the formatted log object.

asObjectBindingsOnly mode already forwards the remaining arguments (return [formattedLogObject, ...argsCloned]), but the regular asObject branch dropped them.

Change

Mirror the asObjectBindingsOnly branch in browser.js and return the remaining (unconsumed) arguments alongside the formatted log object:

return [formattedLogObject, ...argsCloned]

Verification

Added a regression test in test/browser.test.js:

• logger.info('test', { di: 'da' }) now calls write(logObj, { di: 'da' }).

The new test fails on main and passes with this change:

npx tape test/browser.test.js

[luantaraschi]

I reproduced the reported behavior against the parent commit: the custom write function received only the formatted log object. At this head it also receives the untouched { di: 'da' } argument, while the formatted object still contains the expected level, message, and timestamp.

I also ran the complete test/browser.test.js file (196 assertions), ESLint on the changed files, and git diff --check. All passed. The change is limited to forwarding the arguments that remain after the log object is formatted, consistent with the existing asObjectBindingsOnly path.