Fix stale macOS comment in the test pipeline

The build_native.yaml step comment claimed "macOS uses the committed
.dylib and is skipped inside the template." Both halves are now false:
this branch dropped all committed dylibs and added a macOS build step to
build_native.yaml (an active Darwin-conditioned step), so the dylib is
compiled fresh on the mac-aarch64 agent like the .so/.dll. The stale
comment could mislead a maintainer into skipping macOS in the template,
which would hard-break the mac leg since no committed dylib remains.
Reword to state that every platform's binary is built on its own native
agent and none are committed.

Author: bluestreak01

ci/run_tests_pipeline.yaml

@@ -78,10 +78,12 @@ stages:
                 maven | "$(Agent.OS)"
               path: $(HOME)/.m2/repository
             displayName: "Cache Maven repository"
-          # Compile the native libquestdb.so/.dll on the runner (Linux/Windows
-          # binaries are no longer committed). Must run before the client jar is
-          # installed so the freshly built lib is packaged into it. macOS uses
-          # the committed .dylib and is skipped inside the template.
+          # Compile the native libquestdb shared library on the runner; no
+          # platform's binary is committed anymore. Must run before the client
+          # jar is installed so the freshly built lib is packaged into it. The
+          # template builds the right artifact for the current native agent --
+          # Linux (.so), Windows (.dll), and macOS (.dylib) alike (see
+          # build_native.yaml).
           - template: build_native.yaml
           - bash: |
               BRANCH="${SYSTEM_PULLREQUEST_SOURCEBRANCH:-$BUILD_SOURCEBRANCHNAME}"