[lint] Remove no-prototype-builtins

[dayo09]

This commit adds "no-prototype-builtins" rule and
fixes errors accordingly.

ONE-vscode-DCO-1.0-Signed-off-by: dayo09 [email protected]

---

For #1253

Remove no-prototype-builtins

Reference

https://eslint.org/docs/latest/rules/no-prototype-builtins

In ECMAScript 5.1, Object.create was added, which enables the creation of objects with a specified [[Prototype]]. Object.create(null) is a common pattern used to create objects that will be used as a Map. This can lead to errors when it is assumed that objects will have properties from Object.prototype. This rule prevents calling some Object.prototype methods directly from an object.

Additionally, objects can have properties that shadow the builtins on Object.prototype, potentially causing unintended behavior or denial-of-service security vulnerabilities. For example, it would be unsafe for a webserver to parse JSON input from a client and call hasOwnProperty directly on the resulting object, because a malicious client could send a JSON value like {"hasOwnProperty": 1} and cause the server to crash.

To avoid subtle bugs like this, it’s better to always call these methods from Object.prototype. For example, foo.hasOwnProperty("bar") should be replaced with Object.prototype.hasOwnProperty.call(foo, "bar").

Example

Examples of incorrect code for this rule:
var hasBarProperty = foo.hasOwnProperty("bar");
....
Examples of correct code for this rule:
var hasBarProperty = Object.prototype.hasOwnProperty.call(foo, "bar");

[seanshpark]

LGTM thank you!

[dayo09]

@Samsung/one-vscode PTAL :-D

[mhs4670go]

LGTM

[mhs4670go]

it has some confilct.

[dayo09]

@mhs4670go @seanshpark It's rebased. PTAL :-D