chore: use Object.hasOwn for iterator checks

[trivikr]

This relates to...

N/A

Rationale

Use Object.hasOwn() instead of Object.prototype.hasOwnProperty.call() for the remaining own-property checks in the iterator safety helpers. The repository already uses Object.hasOwn() elsewhere, and the current Node engine requirement supports it, so this keeps the codebase more consistent and modern without changing behavior.

Changes

• Replace Object.prototype.hasOwnProperty.call(..., Symbol.iterator) with Object.hasOwn(..., Symbol.iterator) in the shared hasSafeIterator logic
• Update the corresponding helper in the DNS interceptor to use the same pattern

Features

N/A

Bug Fixes

N/A

Breaking Changes and Deprecations

N/A

Status

• I have read and agreed to the Developer's Certificate of Origin
• Tested
• Benchmarked (optional)
• Documented
• Review ready
• In review
• Merge ready

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.94%. Comparing base (6a30f74) to head (60d9b72).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4979   +/-   ##
=======================================
  Coverage   92.94%   92.94%           
=======================================
  Files         110      110           
  Lines       35767    35767           
=======================================
+ Hits        33244    33245    +1     
+ Misses       2523     2522    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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.

[mcollina]

lgtm