[CHANGED] StreamInfo() will now return all subjects when requested

[jnmoyne]

If a subject filter is specified in the StreamInfoRequest{} option,
then all matching subjects will be returned and not be capped to
the server limit of 100,000. It is internally using pagination
that was added in the server PR: nats-io/nats-server#3454

[kozlovic]

At the very least you need to update go_test.mod to the latest version of the server so you can benefit from the feature you added in the server. But I think we can get away with reusing StreamInfo() as opposed to add a new function.

[coveralls]

Coverage increased (+0.03%) to 85.565% when pulling 65796fc on jnm/implement_server_PR_3454 into 866ce08 on main.

[kozlovic]

This is changing the behavior in that it makes all StreamInfo request being a non empty request with an Offset (since I don't think this is omitempty). I would set a boolean in the "if" condition above that at least do the offset setting and marshal ONLY if the o.streamInfoOpts is not nil, or maybe rewrite in a way that you deal with simple info where no subject details is asked first, then deal with the cases where subjects are returned.

[kozlovic]

Technically, here even if user did not ask for details, you are now creating this map and returning as a resp.StreamInfo.State.Subjects (empty, but non nil map). More reasons maybe to treat the two situations differently, or at the very least do the creation only if map is nil AND the aforementioned boolean is set (indicating that we were asking for subject details)