clients: document supervisory/array-write parity gotchas and add advise-supervisory to all CLIs

A consuming project hit two MXAccess parity surprises: a plain Write only
records its user_id when the item has an active supervisory advise (the path
to take when not authenticating), and array writes replace the whole array
rather than patching individual elements. Document both across the five client
READMEs and gateway.md's compatibility baseline, and expose the missing
advise-supervisory subcommand in the go/python/rust/java CLIs (plus the .NET
help text) so callers can establish the supervisory advise without dropping to
the raw command API.

gateway.md

@@ -1049,6 +1049,15 @@ Known important parity areas from existing captures:
 - Invalid handles and cross-server handles have specific exception/status
   behavior.
 - STA message pumping is required for event delivery.
+- A plain `Write`/`Write2` only honors its `user_id` when the item has an active
+  supervisory advise. Callers that do not go through the
+  `AuthenticateUser` → `WriteSecured`/`WriteSecured2` path must send
+  `AdviseSupervisory` for the item before a user id on a plain write is
+  recorded; otherwise the user id is ignored.
+- Writing an array attribute replaces the whole array — it is not an
+  element-wise patch. To change a subset of elements the caller must send the
+  full array (unchanged elements included); sending only the changed elements
+  resizes the attribute.
 
 The gateway should not "fix" these behaviors unless the client explicitly opts
 into a non-parity mode.