Fix: raise status message when doing incorrect pull

[MauriceVanVeen]

Resolves #1194

Simple potential fix is enabling raiseStatusWarnings in the _pull(..).

Would keep the behaviour the same, just informing the user of the status message being hit:

Aug 09, 2024 12:07:58 PM io.nats.client.impl.ErrorListenerLoggerImpl pullStatusWarning
WARNING: pullStatusWarning, Connection: 13, Subscription: 631365415, Consumer Name: 8V2ygPms7b, Status:Status{code=409, message='Exceeded MaxRequestBatch of 1'}

[scottf]

See DM.