Fix wrong initial settings of js ordered consumer

[olbabushkin]

Currently we lost initial settings of ordered consumer if there is OptStartSeq is present.
Just fixed wrong check initial request condition

Also it looks like we will lost initial settings on every consumer reset. The main problem as I see is that policy can be changed from DeliverLastPerSubjectPolicy to DeliverByStartSequencePolicy just by consumer reset. This is very unexpected behavior.
Also lost InactiveThreshold is a bit unpleasant too.

[Jarema]

Hey!

Thank you for your PR and feedback!

We cannot use DeliverLastPerSubject policy on reset, as it would cause redeliveries of messages that were already delivered.

The ByStartSequence would works fine, however there is an edge case if reset happens before we get all initial last per subject messages. We need to think about that one.

Keep in mind thet DeliverPolicy is just the starting condition for the consumer, and the whole point of resetting consumer is to resume when we missed some message, at last know sequence.

Thank you for pointing out the issue with InactiveThreshold - you are right. We should definately persist the original one upon reset.