Concurrent transaction submission to the sequencer throws an error

[ylembachar]

When two transactions are submitted to the sequencer concurrently, both get assigned the same nonce and one doesn't get submitted to the sequencer and throws an error. The actual implementation already uses the pending state when sending the encrypted transaction - when opts.Nonce is nil, it uses the pending state.