[v22.x] src: use std::sort in node_metadata for libc++13 compatibility

[rebroad]

Summary

This replaces std::ranges::sort() with std::sort(begin, end, ...) in src/node_metadata.cc.

Motivation

On armhf + clang-13/libc++13, std::ranges::sort is unavailable, causing Node v22 build failure.

Testing

• Built on armhf (Raspberry Pi 3, 32-bit userspace)
• Command: make -j2

Notes

• No behavior change intended; sorting semantics are unchanged.

[addaleax]

Would be nice to add a note about why this doesn't affect 24.x and above in the commit message, though

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/71324/

[rebroad]

Would be nice to add a note about why this doesn't affect 24.x and above in the commit message, though

I've not looked at 24.x, so it might also affect that.

[addaleax]

@rebroad Why does this PR target v22.x-staging then? That's generally reserved for PRs that either do not make sense on main anymore or backports of commits that otherwise don't cleanly apply on older release lines

[Renegade334]

The build requirements for v22.x are GCC 10.1 / Clang 13 targeting C++17; std::ranges is a C++20 feature that existed in GCC 10 but not until Clang 14, which I guess is the hiccup.