ffi: validate DynamicLibrary getter receivers

[trivikr]

Fixes: #65287

Check the receivers of the path, symbols, and functions getters before unwrapping them. This prevents incompatible receivers from crashing the process and makes the getters throw ERR_INVALID_THIS instead.

---

Assisted-by: codex:gpt-5.6-sol

[nodejs-github-bot]

Review requested:

• @nodejs/ffi

[codecov]

Codecov Report

❌ Patch coverage is 81.25000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.32%. Comparing base (91a99c5) to head (5768e16).
⚠️ Report is 79 commits behind head on main.

Files with missing lines	Patch %	Lines
src/node_ffi.cc	81.25%	0 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #65288      +/-   ##
==========================================
- Coverage   90.32%   90.32%   -0.01%     
==========================================
  Files         751      751              
  Lines      250000   249972      -28     
  Branches    47231    47227       -4     
==========================================
- Hits       225816   225784      -32     
- Misses      15566    15569       +3     
- Partials     8618     8619       +1     

Files with missing lines	Coverage Δ
src/node_ffi.cc	71.05% <81.25%> (+0.31%)	⬆️

... and 26 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.

[nodejs-github-bot]

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

[ShogunPanda]

Are we doing this elsewhere?
The reproduction seems really convolute which means the user is really try to harm him/herself.

[trivikr]

Are we doing this elsewhere?

Yes. Other native accessors use a V8 Signature to enforce the receiver.

node/src/node_url_pattern.cc

Lines 702 to 715 in f83e7df

	// The signature is used to prevent the property accessors from being
	// called on the wrong receiver object (`this`)
	auto signature = Signature::New(isolate, ctor_tmpl);
	instance_template->SetInternalFieldCount(URLPattern::kInternalFieldCount);
	#define ENV_GETTER(lowercase_name) env->lowercase_name##_string()
	#define URL_PATTERN_COMPONENT_GETTERS(uppercase_name, lowercase_name) \
	prototype_template->SetAccessorProperty( \
	ENV_GETTER(lowercase_name), \
	FunctionTemplate::New( \
	isolate, URLPattern::uppercase_name, Local<Value>(), signature), \
	Local<FunctionTemplate>(), \
	attributes);

Should we use signature-based approach here instead of explicit ERR_INVALID_THIS checks?

[trivikr]

Should we use signature-based approach here instead of explicit ERR_INVALID_THIS checks?

I posted an alternative PR for the signature-based approach for easy comparison #65415

[ShogunPanda]

I prefer #65415.