workflows: add dev branch

Fix labeled-response when doing multi-target messages When performing a multi-target PRIVMSG/NOTICE/TAGMSG (i.e. PRIVMSG nick1,nick2 ...) where those targets are on remote servers would cause an assertion failure for opening a remote labeled-response batch while one was already open. Move the logic up to calculate how many servers we're expecting responses from once rather than opening a batch per client.