job限流bug

JobContainer中的异常没有抛出，导致计算channel数量存在潜在异常

```
// 在byte流控情况下，单个Channel流量最大值必须设置，否则报错！
Long channelLimitedByteSpeed = this.configuration
.getLong(CoreConstant.DATAX_CORE_TRANSPORT_CHANNEL_SPEED_BYTE);
if (channelLimitedByteSpeed == null || channelLimitedByteSpeed <= 0) {
// todo 异常没有抛出！！！
DataXException.asDataXException(
FrameworkErrorCode.CONFIG_ERROR,
"在有总bps限速条件下，单个channel的bps值不能为空，也不能为非正数");
}
needChannelNumberByByte =
(int) (globalLimitedByteSpeed / channelLimitedByteSpeed);
needChannelNumberByByte =
needChannelNumberByByte > 0 ? needChannelNumberByByte : 1;
```

Start with the JobContainer byte-flow-control branch shown in the report and inspect the DataXException.asDataXException call together with the two channel-speed configuration values. Done means invalid or missing per-channel byte limits stop channel-count calculation by propagating the configuration error.

Written by the indexing model from the issue text.