re evaluate handling of "maximum subscriptions exceeded" error in go client

[matthiashanel]

When a client subscribes and hits the connection subscriber limit, it appears that the client handles this error with a connection disconnect.
Alternatively, it could surface as subscriber error in a callback but leave the connection alive.

When the limit is lowered retro actively, (jwt or reload) the connection gets disconnected by the server. This is expected.

[wallyqs]

maybe handle same as permissions error? https://github.com/nats-io/nats.go/blob/main/nats.go#L3186