fix(longbridge): convert order writes to SDK Decimal

[RainMona]

Summary

Longbridge submit/replace currently passes decimal.js values into the SDK's native Decimal fields via as unknown as never. The N-API binding cannot unwrap those values, so paper/live order writes fail at submittedQuantity / replace quantity and the matching price fields.

This is an in-house reimplementation of the diagnosis in #959 and the write-boundary conversion proposed in #704. Credit: @fanfpy, added to CONTRIBUTORS.md.

The adapter still uses decimal.js internally. At the Longbridge write boundary it now does new LongbridgeDecimal(value.toString()) for:

• submit: quantity, limit price, trigger price, trailing percent
• replace: quantity, limit price, trigger price

Verification

• pnpm vitest run services/uta/src/domain/trading/brokers/longbridge/LongbridgeBroker.spec.ts — 72/72 passed
• npx tsc --noEmit — passed
• pnpm -F @traderalice/uta-broker-longbridge typecheck — passed
• pnpm test — 4546 passed; 25 unrelated CLI installer / Supervisor PTY failures in this environment (ERR_UNKNOWN_FILE_EXTENSION on packages/cli/bin/openalice.ts)
• Live-paper: not run (no independently verified Longbridge paper account in this environment)

Boundary touch

• trading

Non-goals

• No change to order-type translation, validation, or the Broker Pack API
• Does not merge or cherry-pick the external fix(longbridge): use native Decimal for order writes #704 branch
• Leaves Longbridge broker: order submit/replace fails at N-API boundary — decimal.js values passed to SDK's native Decimal fields #959 and fix(longbridge): use native Decimal for order writes #704 open until this lands

[vercel]

@cursoragent is attempting to deploy a commit to the luokerenx4's Team Team on Vercel.

A member of the Team first needs to authorize it.