docs(bot-detection): add GPU Acceleration to Kernel Features That Help (#346)

* docs(auth): mention GPU acceleration in Managed Auth feature list

Surface the bot-detection benefit of GPU-enabled browsers for login
flows on sites that fingerprint rendering output (canvas/WebGL).

* docs(bot-detection): move GPU acceleration to bot-detection overview

Drop the GPU bullet from the Managed Auth feature list — it belongs
under Kernel Features That Help on the bot-detection overview, where
the other anti-detection levers (stealth, proxies, profiles, computer
controls) are listed.

---------

Co-authored-by: ulziibay-kernel <253135130+ulziibay-kernel@users.noreply.github.com>

Author: ulziibay-kernel

browsers/bot-detection/overview.mdx

@@ -47,6 +47,9 @@ Kernel automatically applies Patchright to remove automation fingerprints, inclu
 Controls the browser without using the Chrome DevTools Protocol (CDP), which can reduce bot detection signals.
 Emulates native keyboard and mouse input directly at the OS level and includes human-like [bezier curves](/browsers/computer-controls#move-the-mouse) by default.
 
+### [GPU Acceleration](/browsers/gpu-acceleration)
+Many detection systems fingerprint canvas and WebGL rendering output and cross-check it against the claimed GPU. Software-rendered browsers produce pixel hashes that don't match any real consumer GPU, which is a strong bot signal on sites with rendering-based fingerprinting. GPU-enabled Kernel browsers render through real hardware, producing output consistent with a normal user's device.
+
 ## Getting Started
 
 Before you start automating your workflow, we recommend that you manually test your website to understand how it behaves with Kernel's browsers. Here's how to do that: