Make prototype pollution attacks harder in most Bun APIs that accept objects

[Jarred-Sumner]

What does this PR do?

Fixes GHSA-5jqh-3v22-8jgj

This makes it so that in most natively-implemented APIs, we ignore prototype chains when calling getters on objects. We deliberately continue to consult prototype chains for Web APIs and node APIs because that would be a clearly breaking change.

This might be a breaking change as-is.

There are probably a few more spots in Bun APIs where we should do this that we aren't, like the shell (which has a JS wrapper).

Let's see if this causes any non-flaky test failures

How did you verify your code works?

There is a test for GHSA-5jqh-3v22-8jgj

[robobun]

❌ @Jarred-Sumner, your commit 24a1d3d has 9 failures in #3834:

test/js/web/streams/streams.test.js - 1 failing on 🍎 14 x64

test/js/node/watch/fs.watch.test.ts - timeout on 🍎 14 x64

test/cli/install/registry/bun-install-registry.test.ts - 1 failing on 🍎 14 x64

test/cli/install/registry/bun-install-registry.test.ts - 1 failing on 🍎 13 x64

test/js/web/fetch/fetch-tcp-stress.test.ts - timeout on 🍎 13 aarch64

test/js/web/fetch/fetch-tcp-stress.test.ts - timeout on 🍎 14 x64

test/cli/hot/watch.test.ts - 1 failing on 🪟 x64

test/cli/hot/watch.test.ts - 1 failing on 🪟 x64-baseline

test/js/node/test/parallel/child-process-exec-timeout-kill.test.js - 1 failing on 🍎 14 aarch64

test/js/node/net/node-net-server.test.ts - 1 failing on 🪟 x64

test/cli/watch/watch.test.ts - 2 failing on 🪟 x64

test/cli/watch/watch.test.ts - 2 failing on 🪟 x64-baseline

test/js/bun/http/bun-serve-static.test.ts - 2 failing on 🍎 13 aarch64