transaction-bench: allow using several endpoints each with it's own keypair

Due to restrictions of the SWQoS on the server side the maximum number of streams per staked connection is 512. We can extend transaction-bench to use several identities instead of one and create a new tpu-client-next scheduler for each (one scheduler owns one endpoint). This also require slight refactoring to use ClientBuilder instead of creating scheduler manually.