permission: support URL and Uint8Array as has()/drop() reference

[nhjbest22]

process.permission.has()/drop() only accepted a string or Buffer for
the reference argument. This adds support for a WHATWG URL, resolved
via fileURLToPath() for fs.* scopes since those are the only scopes
that actually use the reference value, and a plain Uint8Array.

Also switches permission.cc from Utf8Value to BufferValue when reading
a Buffer/TypedArray reference, since Utf8Value forces a UTF-8 string
conversion that can silently corrupt a path that isn't valid UTF-8.

[nodejs-github-bot]

Review requested:

• @nodejs/security-wg

[codecov]

Codecov Report

❌ Patch coverage is 90.69767% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.14%. Comparing base (cf30b2e) to head (42241f8).
⚠️ Report is 194 commits behind head on main.

Files with missing lines	Patch %	Lines
src/permission/permission.cc	72.72%	0 Missing and 3 partials ⚠️
lib/internal/process/permission.js	96.87%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #65492      +/-   ##
==========================================
+ Coverage   90.11%   90.14%   +0.03%     
==========================================
  Files         752      751       -1     
  Lines      251861   252647     +786     
  Branches    47365    47549     +184     
==========================================
+ Hits       226955   227745     +790     
+ Misses      16238    16192      -46     
- Partials     8668     8710      +42     

Files with missing lines	Coverage Δ
lib/internal/process/permission.js	92.39% <96.87%> (+10.68%)	⬆️
src/permission/permission.cc	75.98% <72.72%> (+0.76%)	⬆️

... and 108 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nhjbest22]

@MikeMcC399
Thank you for keeping an eye on this and trying to rerun CI! I also suspect it's an issue with Jenkins CI itself. I noticed many people working hard on Slack to resolve the CI issues as well.

I'll just sit tight and wait for the CI to be resolved.

[nhjbest22]

@MikeMcC399

Thank you so much for constantly keeping an eye on my PR and explaining the CI status! I'm truly amazed by all the care and effort you've put into this.

Based on your explanation, it sounds like we might see a green CI soon! I'll sit tight and wait a bit longer.

[MikeMcC399]

@nhjbest22

Thank you so much for constantly keeping an eye on my PR and explaining the CI status! I'm truly amazed by all the care and effort you've put into this.

Based on your explanation, it sounds like we might see a green CI soon! I'll sit tight and wait a bit longer.

I didn't expect to be spending so much effort surrounding your PR, however it has got caught up in several generic issues, so that's why I'm continuing to follow it and get it resolved together with others on the team.

So far none of the issues seem to come from changes you've proposed in this PR, so I am hopeful to see a green CI soon! Thanks for your patience!

[nodejs-github-bot]

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

[MikeMcC399]

Jenkins is now green after many attempts 🎉. The issues it found had nothing to do with the contents of this PR and these are hidden now as resolved / outdated in the history.

Marking as author ready PRs with CI started, the required approvals, and no outstanding review comments. and handing back to the subject matter experts who approved the PR.