Update the default SubscriberDeliveryTaskCount

[ColinSullivan1]

The SubscriberDeliveryTaskCount default should be set to something sane like 3. Currently it is zero which is too strongly biased toward high throughput with a low number of subscriptions and does not support many subscriptions in one application as one thread to be created per subscription.

This issue has come up a number of times - we should default to scalability over throughput, supporting many subscriptions. It is more common to need many thousands of subscriptions versus millions of messages per second.

Some testing would be appreciated to find a default that would support 1000 subscriptions at 100 msgs/sec on common hardware, like a laptop. It is set here.

See: #449 (comment)