gh-127146: Report uid in Emscripten + node as native uid

[hoodmane]

Fixes test_netrc.NetrcTestCase.test_security, which was getting mad that we reported the uid of a file correctly but reported the user's uid as 0.

cc @freakboy3742.

• Issue: Emscripten: Get test suite passing #127146

[freakboy3742]

!buildbot emscripten

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @freakboy3742 for commit f2a7202 🤖

Results will be shown at:

https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136509%2Fmerge

The command will test the builders whose names match following regular expression: emscripten

The builders matched are:

• WASM Emscripten PR

[freakboy3742]

The buildbot isn't happy with the new C file...

[hoodmane]

Indeed, there is a missing #include.
!buildbot emscripten

[hoodmane]

How do the !buildbot pragmas work? I don't find a section the devguide https://devguide.python.org/testing/buildbots/ Maybe we should add a paragraph there explaining.

[freakboy3742]

!buildbot emscripten

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @freakboy3742 for commit 789681e 🤖

Results will be shown at:

https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136509%2Fmerge

The command will test the builders whose names match following regular expression: emscripten

The builders matched are:

• WASM Emscripten PR

[freakboy3742]

How do the !buildbot pragmas work? I don't find a section the devguide https://devguide.python.org/testing/buildbots/ Maybe we should add a paragraph there explaining.

I'm not sure if the buildbot issue is a permissions thing, or if the buildbot directive has to be a comment on its own. I've asked on Discord for clarification; in the meantime, I've kicked off a build for you.