Client updates to fix bootstrapping and bot-community script for parachain

[clangenb]

Main Changes:

• Instead of implicitly deciding that a sudo/collective call should be composed based on the absence of the signer arg, we do now explicitly add a CLI arg to decide if the new-community call should be wrapped or not.
• additionally, we also explicitly check if the transaction should be sent or not via the dry run flag

There were other smaller fixes necessary for the parachain:

• The tx weight of the parachain is much bigger. I could only batch around 7 add_location calls for a successful proposal. I made this configurable via the -b or --batch-size CLI argument for now, which defaults to 100 so that it is not a breaking change. Note: Interestingly, the error I got for too many locations was misleading:
  • way too many locations: -> TX would exhaust block limit
  • a little bit too much: -> invalid proposal weight (very misleading error)
• For some reason the faucet amount was off, I could only send around 1 transaction with the reasonable_balance. I just added a factor of 100 for now, and decided to not care about it.

Note: I only fixed the new-community command. add-location should have the same logic in the future with respect to wrapping, batching and dry-running the extrinsic, but I thought this should come with a minor refactoring: #388

I manually tested bootstrapping and the bot-community against the parachain, and it works 🥳.

[brenzi]

that's a nice solution

[brenzi]

LGTM