Sui pusher updates

[jayantk]

Two small updates:

1. Flag to avoid sending duplicate transactions. This is a different approach to avoiding concurrent transactions that's sup-specific, as opposed to the previous await PR (which i closed).
2. CLI flag to set the maximum number of VAAs that can be included in a single sui PTB. At the moment, the SUI cost of our PTBs grows superlinearly with the number VAAs, so we want to split price updates into multiple PTBs to keep the costs down.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
example-oracle-amm	⬜️ Ignored (Inspect)			Jun 23, 2023 3:47pm
xc-admin-frontend	⬜️ Ignored (Inspect)			Jun 23, 2023 3:47pm

[ali-behjati]

In general I prefer Map over Record as it's less JS black magic.

[ali-behjati]

Looks good to me. I understand the rationale behind it. Breaking down updates into multiple updates is only possible because we don't override a transaction and we want (and ignore). Maybe it's good to right down the assumptions somewhere in the file.

for me and @0xfirefist It's good if we do it for other networks in another PR too, there are some unintuitive important tricks per network that can easily go out of hand.