fixed consumer restart on source filter update

[matthiashanel]

When a stream source filter subject was updated, the internal consumer was not re created

If the upstream stream contains a tail of previously filtered messages, these will now be delivered

PLEASE check my method to restart and if my use of mset.setSourceConsumer(s.iname, si.sseq+1) is the right thing to do here. Test etc... look al right. just want to point this one out.

[tbeets]

In a server restart scenario, was the internal consumer hydrated with the updated config from store at that time? Is this fix making sure that the config update (source change) happens immediately?

[matthiashanel]

In a server restart scenario, was the internal consumer hydrated with the updated config from store at that time? Is this fix making sure that the config update (source change) happens immediately?

@tbeets yes, happens immediately now