Fix HEAD-SNAPSHOT deployment.

This CL makes the following changes:

  * Updates Sonatype snapshot url for CI action:
    https://central.sonatype.com/repository/maven-snapshots
  * Updates `dev-guide/versions.md` documentation for Gradle setup
  * Updates `workspace_defs.bzl` for Bazel setup

RELNOTES=N/A
PiperOrigin-RevId: 782081321

Author: bcorso

dev-guide/versions.md

@@ -18,7 +18,7 @@ changes at HEAD. Unlike the [Dagger release artifacts](#release-artifacts), the
 `HEAD-SNAPSHOT` artifacts are updated on each commit to the Dagger codebase.
 
 Dagger's `HEAD-SNAPSHOT` artifacts can be found at
-[https://oss.sonatype.org/content/repositories/snapshots/com/google/dagger/](https://oss.sonatype.org/content/repositories/snapshots/com/google/dagger/).
+[https://central.sonatype.com/repository/maven-snapshots/com/google/dagger/](https://central.sonatype.com/repository/maven-snapshots/com/google/dagger/).
 
 We don't recommended using the `HEAD-SNAPSHOT` artifacts in production, but it
 can be used to test out, verify, or just give feedback on features that are not
@@ -40,22 +40,23 @@ dependencies {
 ```
 
 Next, update your plugin and project repositories to include the Sonatype
-snapshot url. This usually goes in your top-level `build.gradle` file. For
-example:
+snapshot url (see
+https://central.sonatype.org/publish/publish-portal-snapshots/#consuming-via-gradle).
+This usually goes in your top-level `build.gradle` file. For example:
 
 ```groovy
 // top-level build.gradle file
 buildscript {
     repositories {
         maven {
-            url "https://oss.sonatype.org/content/repositories/snapshots"
+            url "https://central.sonatype.com/repository/maven-snapshots"
         }
     }
 }
 allprojects {
     repositories {
         maven {
-            url "https://oss.sonatype.org/content/repositories/snapshots"
+            url "https://central.sonatype.com/repository/maven-snapshots"
         }
     }
 }