Support consuming N message in a single command

[zklgame]

For #190.
Support both internal channel command and signal command.

[codecov]

Codecov Report

Merging #198 (e8680ab) into main (757eed4) will increase coverage by 0.12%.
The diff coverage is 77.35%.

@@             Coverage Diff              @@
##               main     #198      +/-   ##
============================================
+ Coverage     71.36%   71.49%   +0.12%     
- Complexity      366      376      +10     
============================================
  Files            59       60       +1     
  Lines          1526     1575      +49     
  Branches        135      139       +4     
============================================
+ Hits           1089     1126      +37     
- Misses          368      379      +11     
- Partials         69       70       +1     

Files Changed	Coverage Δ
...low/core/communication/InternalChannelCommand.java	73.68% <66.66%> (-26.32%)	⬇️
...io/iworkflow/core/communication/SignalCommand.java	73.68% <66.66%> (-26.32%)	⬇️
...n/java/io/iworkflow/core/command/SuperCommand.java	75.00% <75.00%> (ø)
...java/io/iworkflow/core/command/CommandRequest.java	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[longquanzheng]

I feel like it will be much easier to understand/maintain if we create a new structure for this SuperCommand implements BaseCommand.

It's a bit confusing to say, a signal command contain multiple signal commands.
We can just put the helper in this file:

public static SuperCommand create(final String commandId, final String channelName, final int count) {}
public static SuperCommand create(final String channelName, final int count) {}

And the above code in ComandRequest will look cleaner.

[zklgame]

Yes this is better!

[longquanzheng]

You probably not aware of -- there are two usage of commandId:

• for retrieving commandResults, user can use commandId
• more importantly, forAnyCommandCombinationCompleted use commandId to identify different combination.
  Here means all the commands created will share the same commandId. So we probably should make this comment clear here that this is the expectation. Otherwise they use go back to create multiple InternalCommand themselves.