fix(deps): [OCISDEV-834] recover from dead NATS connections in nats-js-kv (stable-8.1)

[kobergj]

Backport of #12401 to stable-8.1.

Problem

The nats-js-kv go-micro store plugin's hasConn() only checked n.conn != nil, not whether the connection was still alive. Once the underlying NATS client exhausted its reconnect attempts (e.g. a NATS pod restart longer than the client's reconnect window), n.conn stayed non-nil but permanently closed. Because initConn() is gated on !hasConn(), it never re-ran, so every subsequent KV operation failed with nats: connection closed until the affected pod was restarted.

This is a base-layer bug in the store plugin used by every oCIS service backed by the NATS KV cache. Confirmed BYCS production manifestations:

• storage-users → ListStorageSpaces: all spaces become invisible to all users (SE-1220, SE-1329, SE-1335)
• ocs → signing-key: 500s, desktop client cannot construct signed download URLs, "X-Request Error downloading Files" (SE-1366)
• sharing pods: same dead-connection symptom (SE-1335)

OPS workaround to date: rolling-restart the affected pod(s).

Fix

This is a dependency bump only. The replace directive for github.com/go-micro/plugins/v4/store/nats-js-kv is pointed at kobergj/plugins commit fc78af4, whose hasConn() now treats a closed connection as no connection:

func (n *natsStore) hasConn() bool {
    return n.conn != nil && !n.conn.IsClosed()
}

so the next operation transparently re-initializes the connection. (See go-micro/plugins#142 for the upstream change.)

No oCIS source changes — only go.mod, go.sum, the re-vendored plugin, and a changelog entry.

Scope note

This backport is intentionally minimal: it ships only the plugin fix, which is the load-bearing change that lets the system self-heal. The complementary hardening discussed in OCISDEV-834 (proactive MaxReconnect=-1 + connection-state handlers in reva's pkg/store and oCIS's natsjsregistry) lands on master only, not on this stable branch.

Refs OCISDEV-834.

[kw-security]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.