[docs-scanner] Missing Docker Desktop limitation in remote access configuration

File: content/manuals/engine/daemon/remote-access.md

Issue

The remote access configuration page provides instructions for configuring the daemon to accept remote connections using daemon.json, but doesn't mention that this configuration method is not supported on Docker Desktop.

The page states:

"You can enable remote access to the daemon either using a docker.service systemd unit file for Linux distributions using systemd. Or you can use the daemon.json file, if your distribution doesn't use systemd."

And later provides detailed instructions for:

"### Configuring remote access with daemon.json

1. Set the hosts array in the /etc/docker/daemon.json to connect to the Unix socket and an IP address..."

However, content/manuals/engine/daemon/troubleshoot.md contains this important limitation:

"Setting hosts in the daemon.json isn't supported on Docker Desktop for Windows or Docker Desktop for Mac."

Why this matters

A Docker Desktop user following the remote-access.md instructions would configure hosts in their daemon.json file, restart Docker, and encounter a failure without understanding why. The limitation is documented, but only in the troubleshooting guide, not in the how-to guide where users would naturally look first.

Suggested fix

Add a note or important callout near the beginning of the "Configuring remote access with daemon.json" section stating:

> [!NOTE]
>
> This configuration method is not supported on Docker Desktop.
> If you're using Docker Desktop, refer to the [settings page](/manuals/desktop/settings-and-maintenance/settings.md) for configuration options.

Or add it to the introduction before the "Configuring remote access with systemd unit file" section to warn readers upfront.

Found by nightly documentation quality scanner

Start with content/manuals/engine/daemon/remote-access.md and compare its daemon.json instructions with the Docker Desktop limitation in content/manuals/engine/daemon/troubleshoot.md. Add a clear note in the remote-access section, including the referenced Desktop settings page, then verify the Markdown and link render correctly.