Update command reference with beta tags

docs/en/ingest-management/commands.asciidoc

@@ -28,14 +28,14 @@ invoking the wrong binary.
 * <<elastic-agent-help-command,help>>
 * <<elastic-agent-inspect-command,inspect>>
 * <<elastic-agent-install-command,install>>
-* <<elastic-agent-privileged-command,privileged>>
+* <<elastic-agent-privileged-command,privileged>> [technical preview]
 * <<elastic-agent-restart-command,restart>>
 * <<elastic-agent-run-command,run>>
 * <<elastic-agent-status-command,status>>
 * <<elastic-agent-uninstall-command,uninstall>>
 * <<elastic-agent-upgrade-command,upgrade>>
 * <<elastic-agent-logs-command,logs>>
-* <<elastic-agent-unprivileged-command,unprivileged>>
+* <<elastic-agent-unprivileged-command,unprivileged>> [technical preview]
 * <<elastic-agent-version-command,version>>
 //* <<elastic-agent-watch-command,watch>>
 
@@ -527,6 +527,8 @@ elastic-agent inspect components log-default
 [[elastic-agent-privileged-command]]
 == elastic-agent privileged
 
+preview::[]
+
 Run {agent} with full superuser privileges.
 This is the usual, default running mode for {agent}.
 The `privileged` command allows you to switch back to running an agent with full administrative privileges when you have been running it in `unprivileged` mode. 
@@ -1102,6 +1104,8 @@ elastic-agent uninstall
 [[elastic-agent-unprivileged-command]]
 == elastic-agent unprivileged
 
+preview::[]
+
 Run {agent} without full superuser privileges.
 This is useful in organizations that limit `root` access on Linux or macOS systems, or `admin` access on Windows systems.
 For details and limitations for running {agent} in this mode, refer to {fleet-guide}/elastic-agent-unprivileged.html[Run {agent} without administrative privileges].