chore: update refs to bazel-lib which moved to bazel-contrib (#1976)

Author: gregmagolan

docs/README.md

@@ -165,7 +165,7 @@ copied to this location.
 Our custom rules will take care of copying their sources to the `bazel-bin` output folder automatically.
 However this only works when those sources are under the same `BUILD` file as the target that does
 the copying. If you have a source file in another `BUILD` file, you'll need to explicitly copy that
-with a rule like [`copy_to_bin`](https://docs.aspect.build/aspect-build/bazel-lib/v1.0.0/docs/copy_to_bin-docgen.html#copy_to_bin).
+with a rule like [`copy_to_bin`](https://docs.aspect.build/bazel-contrib/bazel-lib/v1.0.0/docs/copy_to_bin-docgen.html#copy_to_bin).
 
 **API docs:**
 

docs/faq.md

@@ -152,4 +152,4 @@ my-workspace/
 
 Note that when following option 2, it might require updating some configuration files which refer to the original output locations. For example, your `tsconfig.json` file might have a `paths` section which points to the `../../dist` folder.
 
-To keep your legacy build system working during the migration, you might want to avoid changing those configuration files in-place. For this purpose, you can use [the `jq` rule](https://docs.aspect.build/aspect-build/bazel-lib/v1.0.0/docs/jq-docgen.html#jq) in place of `copy_to_bin`, using a `filter` expression so the copy of the configuration file in `bazel-bin` that's used by the Bazel build can have a different path than the configuration file in the source tree.
+To keep your legacy build system working during the migration, you might want to avoid changing those configuration files in-place. For this purpose, you can use [the `jq` rule](https://docs.aspect.build/bazel-contrib/bazel-lib/v1.0.0/docs/jq-docgen.html#jq) in place of `copy_to_bin`, using a `filter` expression so the copy of the configuration file in `bazel-bin` that's used by the Bazel build can have a different path than the configuration file in the source tree.

docs/js_binary.md

@@ -219,7 +219,7 @@ npm_translate_lock(
 ```
 
 Patching applied by rules_js may slightly deviate from standard pnpm patching behavior.
-The [bazel-lib patch util](https://docs.aspect.build/rulesets/aspect_bazel_lib/docs/repo_utils/#patch)
+The [bazel-lib patch util](https://github.com/bazel-contrib/bazel-lib/blob/main/docs/repo_utils.md#patch)
 is used for patching within rules_js instead of the internal pnpm patching mechanism.
 For example a bad patch file may be partially applied when using pnpm outside of bazel but fail
 when applied by rules_js, see [rules_js #1915](https://github.com/aspect-build/rules_js/issues/1915).
@@ -374,7 +374,7 @@ The tradeoffs are similar to
 [this rules_python thread](https://github.com/bazelbuild/rules_python/issues/608).
 
 In a BUILD file, use a rule like
-[write_source_files](https://github.com/aspect-build/bazel-lib/blob/main/docs/write_source_files.md)
+[write_source_files](https://github.com/bazel-contrib/bazel-lib/blob/main/docs/write_source_files.md)
 to copy the generated file to the repo and test that it stays updated:
 
 ```starlark

docs/js_run_binary.md

@@ -109,7 +109,7 @@ _ATTRS = {
         This must be a target that provides a single file or a `DirectoryPathInfo`
         from `@aspect_bazel_lib//lib::directory_path.bzl`.
         
-        See https://github.com/aspect-build/bazel-lib/blob/main/docs/directory_path.md
+        See https://github.com/bazel-contrib/bazel-lib/blob/main/docs/directory_path.md
         for more info on creating a target that provides a `DirectoryPathInfo`.
         """,
         mandatory = True,

docs/pnpm.md

@@ -1,6 +1,6 @@
 """Runs a js_binary as a build action.
 
-This macro wraps Aspect bazel-lib's run_binary (https://github.com/aspect-build/bazel-lib/blob/main/lib/run_binary.bzl)
+This macro wraps Aspect bazel-lib's run_binary (https://github.com/bazel-contrib/bazel-lib/blob/main/lib/run_binary.bzl)
 and adds attributes and features specific to rules_js's js_binary.
 
 Load this with,
@@ -71,7 +71,7 @@ def js_run_binary(
         tool: The tool to run in the action.
 
             Should be a `js_binary` rule. Use Aspect bazel-lib's run_binary
-            (https://github.com/aspect-build/bazel-lib/blob/main/lib/run_binary.bzl)
+            (https://github.com/bazel-contrib/bazel-lib/blob/main/lib/run_binary.bzl)
             for other *_binary rule types.
 
         env: Environment variables of the action.

js/private/js_binary.bzl

@@ -25,5 +25,5 @@ def rules_js_dependencies():
         name = "aspect_bazel_lib",
         sha256 = "f93d386d8d0b0149031175e81df42a488be4267c3ca2249ba5321c23c60bc1f0",
         strip_prefix = "bazel-lib-2.9.1",
-        url = "https://github.com/aspect-build/bazel-lib/releases/download/v2.9.1/bazel-lib-v2.9.1.tar.gz",
+        url = "https://github.com/bazel-contrib/bazel-lib/releases/download/v2.9.1/bazel-lib-v2.9.1.tar.gz",
     )

js/private/js_run_binary.bzl

@@ -29,7 +29,7 @@ def rules_js_register_toolchains(
     https://docs.aspect.build/rulesets/rules_nodejs/docs/core#node_repositories.
 
     Additional required toolchains (jq, yq, copy_directory and copy_to_directory) come
-    from [Aspect bazel-lib](https://docs.aspect.build/rulesets/aspect_bazel_lib).
+    from [Aspect bazel-lib](https://github.com/bazel-contrib/bazel-lib).
 
     Args:
         node_download_auth: Auth to use for all url requests when downloading Node