fix: include totals in fresh twap

[kernelwhisperer]

Summary

Fix temporary TWAP fetch failures immediately after order creation.

New TWAP parents previously had additionalData: null until the indexer discovered a part. The SDK requires execution totals, so one new parent caused the entire page to fail validation with Invalid GraphQL page: twapOrders.

It's easier to fix it here than the SDK.

Changes

• Initialize TWAP execution totals to "0" during parent creation.
• Reuse the existing ZERO_TOTALS constant.
• Keep other order types unchanged.

How to Test

• 1. Connect the frontend to an indexer with this fix.
• 2. Create an EOA TWAP and open the orders table before its first part appears.
• 3. Confirm that the parent appears with 0% filled and no Invalid GraphQL page: twapOrders console errors.
• 4. After a part fills, confirm that the execution totals and fill percentage update.

Checklist

• Tests pass locally — 187 existing tests
• Linting passes — changed files
• Documentation updated (if needed)
• Breaking changes documented (if any)

Breaking Changes

None

Related Issues

None