Add and update documentation

Signed-off-by: David Festal <dfestal@redhat.com>
Assisted-by: Cursor

docs/tooling/cli/02-build-system.md

@@ -270,6 +270,12 @@ that are exported from the package, leaving a much cleaner type definition file
 and making sure that the type definitions are in sync with the generated
 JavaScript.
 
+### Building Module Federation Remotes
+
+Frontend plugin packages can be built as module federation remotes, which allows them to be loaded dynamically at runtime by a module federation host (typically your main frontend app). To build a package as a module federation remote, use the `--module-federation` option with the `package build` command.
+
+More details are given in the [Module Federation](../../frontend-system/building-apps/07-module-federation.md#building-module-federation-remotes) documentation.
+
 ## Bundling
 
 The goal of the bundling process is to combine multiple packages together into a

docs/tooling/cli/03-commands.md

@@ -200,6 +200,7 @@ Options:
   --skip-build-dependencies  Skip the automatic building of local dependencies. Applies to backend packages only.
   --stats                    If bundle stats are available, write them to the output directory. Applies to app packages only.
   --config <path>            Config files to load instead of app-config.yaml. Applies to app packages only. (default: [])
+  --module-federation        Build a package as a module federation remote. Applies to frontend plugin packages only.
 ```
 
 ## package lint