Fix when using Cluster+Group+Expiration

• Fixed an issue when using Clustering in a Group with maxConcurrent greater than 0 with jobs having an expiration time. A job timing out in a limiter in the group would lower the count of running jobs in all limiters in the group, which would result in going over the rate limit.
• Improved the error message when returning a non-Promise value to schedule()