docs: document limit and disable-resolvability-validation in subgraph check and publish (wundergraph#2674)

Author: JivusAyrus

docs-website/cli/subgraph/check.mdx

@@ -61,10 +61,12 @@ The `npx wgc subgraph check` command checks for breaking changes and composition
 
 * `-o, --out [string]`: Writes the JSON check result to a destination file. This option enables JSON output automatically.
 
-* `--suppress-warnings`: This flag suppresses any warnings produced by composition.
-
 * `--label [labels...]`: The labels to apply to the new subgraph. The labels are passed in the format `<key>=<value> <key>=<value>`. This parameter is always ignored if the subgraph already exists.
 
+* `--disable-resolvability-validation`: This flag disables the validation for whether all nodes of the federated graph are resolvable. Do not use unless troubleshooting.
+
+* `-l, --limit [number]`: The maximum number of entries to display for each category of results, such as schema changes, composed schema breaking changes, composition errors, composition warnings, lint issues, and graph pruning issues. Defaults to `50`.
+
 <Info>
    The check command requires either the `--schema` or `--delete` parameter.
 </Info>

docs-website/cli/subgraph/publish.mdx

@@ -99,6 +99,10 @@ A previously created [Event-Driven Graph (EDG)](/federation/event-driven-federat
 
 * `--suppress-warnings`: This flag suppresses any warnings produced by composition.
 
+* `--disable-resolvability-validation`: This flag disables the validation for whether all nodes of the federated graph are resolvable. Do not use unless troubleshooting.
+
+* `-l, --limit <number>`: The maximum number of entries to display for each category of results, such as composition errors, composition warnings, and deployment errors. Defaults to `50`.
+
 ## **Example**
 
 ### Publish a schema to an existing subgraph.