Update https://bazel.build/rules/performance about where to get the a…

…llocation instrumenter jar file

Fixes #18467

PiperOrigin-RevId: 549334880
Change-Id: Ibc37c2ddd5710f18fc936de3bc8941ac440dc9b1

site/en/rules/performance.md

@@ -218,11 +218,13 @@ You must pass these two startup flags to *every* Bazel invocation:
 
   ```
   STARTUP_FLAGS=\
-  --host_jvm_args=-javaagent:$(BAZEL)/third_party/allocation_instrumenter/java-allocation-instrumenter-3.3.0.jar \
+  --host_jvm_args=-javaagent:<path to java-allocation-instrumenter-3.3.0.jar> \
   --host_jvm_args=-DRULE_MEMORY_TRACKER=1
   ```
-Note: The bazel repository comes with an allocation instrumenter.
-Make sure to adjust `$(BAZEL)` for your repository location.
+Note: You can download the allocation instrumenter jar file from [Maven Central
+Repository][allocation-instrumenter-link].
+
+[allocation-instrumenter-link]: https://repo1.maven.org/maven2/com/google/code/java-allocation-instrumenter/java-allocation-instrumenter/3.3.0
 
 These start the server in memory tracking mode. If you forget these for even
 one Bazel invocation the server will restart and you will have to start over.