nodejs-16_x: 16.15.0 -> 16.16.0

[marsam]

Description of changes

https://github.com/nodejs/node/releases/tag/v16.15.1
https://github.com/nodejs/node/releases/tag/v16.16.0

Fixes #176127

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.11 Release Notes (or backporting 22.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[marsam]

@GrahamcOfBorg build hedgedoc

[github-actions]

Backport failed for release-22.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git fetch origin release-22.05
git worktree add -d .worktree/backport-182431-to-release-22.05 origin/release-22.05
cd .worktree/backport-182431-to-release-22.05
git checkout -b backport-182431-to-release-22.05
ancref=$(git merge-base 2d372784634e224c5a629d80a19705af655fbc7d 37580d6187057ee9a8fbce185f4b6e6e708a2316)
git cherry-pick -x $ancref..37580d6187057ee9a8fbce185f4b6e6e708a2316

[github-actions]

Backport failed for release-22.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git fetch origin release-22.05
git worktree add -d .worktree/backport-182431-to-release-22.05 origin/release-22.05
cd .worktree/backport-182431-to-release-22.05
git checkout -b backport-182431-to-release-22.05
ancref=$(git merge-base 2d372784634e224c5a629d80a19705af655fbc7d 37580d6187057ee9a8fbce185f4b6e6e708a2316)
git cherry-pick -x $ancref..37580d6187057ee9a8fbce185f4b6e6e708a2316

[Izorkin]

@marsam this patch don't fixed error:

peertube-start[77762]: > peertube@4.2.1 start
peertube-start[77762]: > node dist/server
peertube-start[77762]: npm ERR! code EROFS
peertube-start[77762]: npm ERR! syscall mkdir
peertube-start[77762]: npm ERR! path /nix/store/0nwdj4gq20h0r15r36rl6603jaj46myn-peertube-4.2.1/.npm
peertube-start[77762]: npm ERR! errno -30
peertube-start[77762]: npm ERR! rofs EROFS: read-only file system, mkdir '/nix/store/0nwdj4gq20h0r15r36rl6603jaj46myn-peertube-4.2.1/.npm'
peertube-start[77762]: npm ERR! rofs Often virtualized file systems, or other file systems
peertube-start[77762]: npm ERR! rofs that don't support symlinks, give this error.
peertube-start[77762]: npm ERR! Log files were not written due to an error writing to the directory: /nix/store/0nwdj4gq20h0r15r36rl6603jaj46myn-peertube-4.2.1/.npm/_logs
peertube-start[77762]: npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
systemd[1]: peertube.service: Main process exited, code=exited, status=226/NAMESPACE
systemd[1]: peertube.service: Failed with result 'exit-code'.