ls-apis: mention related RFDs and sections (#8324)

The existing comments in `api-manifest.toml` were helpful, but I'd had a hard
time determining the difference between "versioned_how", versioning mechanisms
described in `openapi-manager`, and the words in RFD 532. Additionally, 532 and 
`api-manifeset.toml` talk about "updated before", and RFD 565 says more about
the update sequence, so point to it as well.

Author: iximeow

dev-tools/ls-apis/README.adoc

@@ -95,7 +95,7 @@ Crucible Pantry
 The `servers` and `deployment-units` commands accept a `--dot` argument to print output in a format that `dot(1)` can process:
 
 ```
-$ cargo xtask ls-apis deployment-units --dot > deployment-units.dot
+$ cargo xtask ls-apis deployment-units --output-format dot > deployment-units.dot
 ```
 
 You can generate a PNG image of the graph like this:

dev-tools/ls-apis/api-manifest.toml

@@ -149,6 +149,13 @@ packages = [ "oximeter-collector" ]
 #              tooling supports this value so that during development you can
 #              relax these constraints.
 #
+# "server" and "client" versioning is elaborated on more in RFD 532.  Note that
+# "lockstep" collapses into "server" here, as it's trivially the case that if
+# the server and client(s) are updated atomically the server does not have to
+# support older clients.  Additionally, the "updated before" relationship is
+# discussed some in RFD 565, [Update
+# sequence](https://rfd.shared.oxide.computer/rfd/0565#_update_sequence).
+#
 # [`versioned_how_reason`]: free text string explaining why `versioned_how` must
 # be "client" for this API.  This is printed in documentation and command output
 # and serves as documentation for developers to understand why we made this