Watermarks should not be activated when neither queue size nor watermarks are configured

When creating an initiator or an acceptor (both synchronous and thread-per-session) without specifying either queue size or watermarks, the watermark tracker is still created and is working incorrectly immediately blocking the reads (queue size 0 is > upper watermark of -1).

Watermarks should only be activated when the queue size is not specified and both lower and upper watermarks are configured to values > 0.

Pull request (code change + tests) - https://github.com/quickfix-j/quickfixj/pull/213