fix: update broken registry.bazel.build/docs URLs (#3926)

## Summary

The `registry.bazel.build/docs/<name>` URL pattern returns 404 and is no
longer valid.

The correct URL format is now
`registry.bazel.build/modules/<name>/latest/docs`.

This was identified across multiple Bazel rule repositories — see
hermeticbuild/rules_rs#235 for the original fix.

## Changes

Updated all occurrences of the broken `/docs/<name>` URL pattern to the
new `/modules/<name>/latest/docs` format.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Update Node.js Versions (#3920)

- Updated Node.js Versions using `npm run update-nodejs-versions`

Auto-generated by [create-pull-request][1]

[1]: https://github.com/peter-evans/create-pull-request

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

chore: update Node.js Versions (#3908)

- Updated Node.js Versions using `npm run update-nodejs-versions`

Auto-generated by [create-pull-request][1]

[1]: https://github.com/peter-evans/create-pull-request

Co-authored-by: alexeagle <47395+alexeagle@users.noreply.github.com>

chore: update gha deps (#3892)

## PR Checklist

Please check if your PR fulfills the following requirements:

- [x] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)


## PR Type

What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->

- [ ] Bugfix
- [ ] Feature (please, look at the "Scope of the project" section in the
README.md file)
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [x] CI related changes
- [ ] Documentation content changes
- [ ] Other... Please describe:


## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or
link to a relevant issue. -->

Issue Number: N/A


## What is the new behavior?


## Does this PR introduce a breaking change?

- [ ] Yes
- [x] No


<!-- If this PR contains a breaking change, please describe the impact
and migration path for existing applications below. -->


## Other information

chore: Update Node.js Versions (December 2025 Security Releases) (#3890)

- Updated Node.js versions using `npm run update-nodejs-versions`
- Adds Node.js v20.20.0, v22.22.0, and v24.13.0 (December 2025 security
releases)

Related to the December 2025 security releases:
https://nodejs.org/en/blog/vulnerability/december-2025-security-releases

Remove target constraint (#3879)

Because `rules_js` 3.x started consuming the runtime toolchain, this
constraint is no longer needed. It is in fact problematic now because it
prevents building multi-platform images.

See:
#3854 
aspect-build/rules_js#2499

## PR Checklist

Please check if your PR fulfills the following requirements:

- [x] Tests for the changes have been added (for bug fixes / features)
- [x] Docs have been added / updated (for bug fixes / features)


## PR Type

What kind of change does this PR introduce?

- [x] Bugfix
- [ ] Feature (please, look at the "Scope of the project" section in the
README.md file)
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Documentation content changes
- [ ] Other... Please describe:


## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or
link to a relevant issue. -->

Issue Number: #3854 


## What is the new behavior?


## Does this PR introduce a breaking change?

- [ ] Yes
- [x] No


<!-- If this PR contains a breaking change, please describe the impact
and migration path for existing applications below. -->


## Other information

Slack: https://bazelbuild.slack.com/archives/CEZUUKQ6P/p1763167547013579

Update Node.js Versions (#3875)

- Updated Node.js Versions using `npm run update-nodejs-versions`

Auto-generated by [create-pull-request][1]

[1]: https://github.com/peter-evans/create-pull-request

Co-authored-by: alexeagle <alexeagle@users.noreply.github.com>

Revert "chore: bazelrc presets (#3865)"

This reverts commit 4b4e2ec.

fix: include docs in source.json

try again to fix CI (#3871)