fix(helpers): Use hasOwnProperty.call

[rbuckton]

This replaces #37013 as I was unable to push up changes to that PR. Thanks @ExE-Boss!

From @ExE-Boss:

Currently, the following code:

exports.hasOwnProperty(…) override

// func-util.ts
export const { apply, call } = (({ apply }) => ({
	apply: <T, A extends any[], R>(
		target: (this: T, ...args: A) => R,
		thisArg: T,
		args: A = [] as A
	): R => apply(target, thisArg, args),
	call: <T, A extends any[], R>(
		target: (this: T, ...args: A) => R,
		thisArg: T,
		...args: A
	): R => apply(target, thisArg, args),
}))(Reflect);

// helpers.ts
import { assertArgs, assertObject } from "./types.js";
import { call } from "./func-util.js";

export * from "./func-util.js";
export const {
	hasOwnProperty,
	isPrototypeOf,
} = (({ hasOwnProperty, isPrototypeOf }) => {
	return {
		hasOwnProperty(target: object, property: PropertyKey) {
			assertArgs(arguments.length, 2);
			assertObject(target);
			return call(hasOwnProperty, target, property);
		},
		isPrototypeOf(proto: object, target: any) {
			assertArgs(arguments.length, 2);
			assertObject(proto);
			return call(isPrototypeOf, proto, target);
		},
	};
})(Object.prototype);

results in an error at runtime when transpiled to non‑ESM, because exports.hasOwnProperty(…) is called with only a single non‑object argument.

---

This also won't work in case exports has its prototype set to null

---

TSLib PR: microsoft/tslib#92

Replaces #37013
Fixes #37016
Fixes #3197

[weswigham]

Yeah, I was always confused why some helpers did use the prototype method and some did not.

[rbuckton]

The tslib side of this change has been merged as well.