Consume semantics - multiple partitions request issue

[markpapadakis]

If, in a single consume request, you request content from two partitions, and one of them does not exist, and the other has no data (will need to tail), like so:

        client.consume(
                {
                        { {_S8("foo_filtered"), 1}, { UINT64_MAX, 1e5 } },
                        { {_S8("foo"), 0}, { UINT64_MAX, 1e5 } },
                }, 1e3, 0);

Tank will respond immediately with not-found for foo_filtrered:1, but it will not register a watch for foo:0 (which is defined). This is correct, however, we don't get information about foo:0 in the response.

[markpapadakis]

• [x] if (deferList.size() && respondNow == true) we need to patch the response
• [x] If we register multiple watches (for multiple partitions), as soon as any of those watches is triggered, we need to forget all other watches for the same request
• [x] We need special care for abort watch

[markpapadakis]

To reproduce, based on the consume() call example used in this issue, make sure that the first partition is undefined, and the later is defined.

[markpapadakis]

Fixed.