feat(cli): add publish batch method for cli sdk

[0xmad]

Description

Add publish batch method for maci-cli sdk.

Additional Notes

N/A

Related issue(s)

Related to privacy-scaling-explorations/maci-platform#7

Confirmation

• I have read and understand MACI's contributor guidelines and code of conduct.
• I have read and understand MACI's GitHub processes.
• I have read and understand MACI's testing guide.

[netlify]

✅ Deploy Preview for maci-typedoc ready!

Name	Link
🔨 Latest commit	843fe7e
🔍 Latest deploy log	https://app.netlify.com/sites/maci-typedoc/deploys/65ddf87e23dfa60008650427
😎 Deploy Preview	https://deploy-preview-1251--maci-typedoc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kittybest]

maybe also add publish test cmd in package.json?

[0xmad]

maybe also add publish test cmd in package.json?

Unit tests can be run via test:unit command.

[kittybest]

maybe also add publish test cmd in package.json?

Unit tests can be run via test:unit command.

I mean something like test:publish? since I saw there are commands for other single unit test

[0xmad]

maybe also add publish test cmd in package.json?

Unit tests can be run via test:unit command.

I mean something like test:publish? since I saw there are commands for other single unit test

Ok, why do you need it? If I run tests for cli, I just run all the tests to make sure if nothing is broken.

[kittybest]

maybe also add publish test cmd in package.json?

Unit tests can be run via test:unit command.

I mean something like test:publish? since I saw there are commands for other single unit test

Ok, why do you need it? If I run tests for cli, I just run all the tests to make sure if nothing is broken.

ok, then never mind.

[ctrlc03]

I see the point of using the same key here for all messages in the batch, we just assume that all messages in the batch are from the same user either way for simplicity sake (though that doesn't necessarily have to be the case), so I would suggest we move line 226 out of the loop to avoid computing the ECDH key every time; and also we should probably return this key like we do in publishMessage.