docs: remove stale v23 framing from BuildKit overview (fixes #24606)

The Getting started section framed Docker Engine v23.0 as a recent dividing
line and included instructions for enabling BuildKit on older versions.
Removed the pre-23.0 enable instructions and simplified to state that
BuildKit is the default builder, with a note that Windows containers still
use the legacy builder.

Co-Authored-By: Claude <noreply@anthropic.com>

Author: dvdksn

content/manuals/build/buildkit/_index.md

@@ -7,10 +7,7 @@ keywords: build, buildkit
 
 ## Overview
 
-[BuildKit](https://github.com/moby/buildkit)
-is an improved backend to replace the legacy builder. BuildKit is the default builder
-for users on Docker Desktop, and Docker Engine as of version 23.0.
-
+[BuildKit](https://github.com/moby/buildkit) is the builder backend used by Docker.
 BuildKit provides new functionality and improves your builds' performance.
 It also introduces support for handling more complex scenarios:
 
@@ -73,39 +70,8 @@ BuildKit, you would
 
 ## Getting started
 
-BuildKit is the default builder for users on Docker Desktop and Docker Engine
-v23.0 and later.
-
-If you have installed Docker Desktop, you don't need to enable BuildKit. If you
-are running a version of Docker Engine version earlier than 23.0, you can enable
-BuildKit either by setting an environment variable, or by making BuildKit the
-default setting in the daemon configuration.
-
-To set the BuildKit environment variable when running the `docker build`
-command, run:
-
-```console
-$ DOCKER_BUILDKIT=1 docker build .
-```
-
-> [!NOTE]
->
-> Buildx always uses BuildKit.
-
-To use Docker BuildKit by default, edit the Docker daemon configuration in
-`/etc/docker/daemon.json` as follows, and restart the daemon.
-
-```json
-{
-  "features": {
-    "buildkit": true
-  }
-}
-```
-
-If the `/etc/docker/daemon.json` file doesn't exist, create new file called
-`daemon.json` and then add the following to the file. And restart the Docker
-daemon.
+BuildKit is the default builder for Docker Desktop and Docker Engine users.
+If you're building Windows containers, the legacy builder is used instead.
 
 ## BuildKit on Windows
 
@@ -180,11 +146,13 @@ see [GitHub issues](https://github.com/moby/buildkit/issues?q=is%3Aissue%20state
    $Env:Path = [System.Environment]::GetEnvironmentVariable("Path","Machine") + ";" + `
        [System.Environment]::GetEnvironmentVariable("Path","User")
    ```
+
 6. Start the BuildKit daemon.
 
    ```console
    > buildkitd.exe
    ```
+
    > [!NOTE]
    > If you are running a _dockerd-managed_ `containerd` process, use that instead, by supplying the address:
    > `buildkitd.exe --containerd-worker-addr "npipe:////./pipe/docker-containerd"`