NATS JetStream doesn't detect a leader change

[JorTurFer]

Report

Currently, if there is a change in the leader due to any reason (manual step-down, disruptions, rotations, etc...) KEDA doesn't detect the change and still request the info to the same node. When a node isn't the consumer leader, it only exposes the current information about in-flight messages. This means that I can have 10k messages pending, but if the node is only processing 100 (because the consumer doesn't allow more), KEDA will see only those 100 instead of the 10k.

Expected Behavior

KEDA should switch to the new leader automatically

Actual Behavior

KEDA is stuck using the old leader