cmd/headscale: rename the database-bypass flag off gRPC

--bypass-grpc-and-access-database-directly is now
--bypass-server-and-access-database-directly; the gRPC server it named is
gone.

docs/about/faq.md

@@ -152,9 +152,9 @@ See also <https://tailscale.com/docs/concepts/device-visibility>.
 Headscale checks if the policy is valid during startup and refuses to start if it detects an error. The error message
 indicates which part of the policy is invalid. Follow these steps to fix your policy:
 
-- Dump the policy to a file: `headscale policy get --bypass-grpc-and-access-database-directly > policy.json`
+- Dump the policy to a file: `headscale policy get --bypass-server-and-access-database-directly > policy.json`
 - Edit and fixup `policy.json`. Use the command `headscale policy check --file policy.json` to validate the policy.
-- Load the modified policy: `headscale policy set --bypass-grpc-and-access-database-directly --file policy.json`
+- Load the modified policy: `headscale policy set --bypass-server-and-access-database-directly --file policy.json`
 - Start Headscale as usual.
 
 !!! warning "Full server configuration required"

docs/v1-ogen/CHANGES.md

@@ -99,6 +99,16 @@ an empty object.
 **Client impact:** scripts parsing the empty `{}` should read the `result`
 field (machine-readable output) or rely on the exit code.
 
+### CLI database-bypass flag renamed
+
+**What:** `--bypass-grpc-and-access-database-directly` is now
+`--bypass-server-and-access-database-directly`.
+
+**Why:** the gRPC server is gone; the flag bypasses the running server whatever
+its transport, so the name no longer mentions gRPC.
+
+**Client impact:** scripts using the old flag name must update it.
+
 ### Missing resources return a consistent `404`
 
 **What:** renaming or expiring an unknown node, and expiring or deleting an