🐛 Fix hasOwn function implementation to ensure proper property checking

In browsers that lack native `Object.hasOwn` support, assigning `Object.prototype.hasOwnProperty.call` to a variable (e.g., hasOwn = `Object.prototype.hasOwnProperty.call`) detaches the `call` method from its original function context. This results in a runtime error: `hasOwn is not a function`.