Support get (up to) N or all messages from channel in one command

### Problem and Use case
A good use case -- kicking off N number states running in parallel, but also want to wait for them to complete.
So each state will publish a message to a channel to tell it's completed. Now if we also want to wait for something else, e.g. a timer for reminder, then it will be quite tricky to wait for One timer OR N messages.

Ideally, it should be just using a single command for N messages:
```
public CommandRequest waitUntil( Integer numOfWaits...){
return CommandRequest.forAnyComandCompleted(
TimerCommand.create(...),
InternalChannelCommand.create( ChannelName, numOfWaits)
);
}
```

But today it needs to use N commands with anyCommandCombination:
```
public CommandRequest waitUntil( Integer numOfWaits...){
return CommandRequest.forAnyComandCombinationCompleted(
CommandCombination.create( ["timerCmdId"], ["msg1CmdId", "msg2CmdId, ...],
TimerCommand.create("timerCmdId", ...),
InternalChannelCommand.create("msg1CmdId", ChannelName ),
InternalChannelCommand.create("msg2CmdId", ChannelName )
...
);
}
```
Or using array:
```
List commandList = new ArrayList()
commandList.add(TimerCommand.create("timerCmdId", ...));
List commandIdList = new ArrayList();
commandIdList.add("timerCmdId");
for(i=0;i

Start with service/interpreter/workflowImpl.go around line 618 and trace how repeated channel commands consume messages. Review the CommandRequest and InternalChannelCommand paths to define the behavior for OneToAll, ZeroToAll, and a fixed N. Done means the requested messages are consumed atomically rather than partially consumed before waiting.

Written by the indexing model from the issue text.