fix: Use static Reflect methods in nodeGlobalThis proxy

[kamilogorek]

  get(_target, prop, _receiver) {
    if (prop in nodeGlobals) {
      return nodeGlobals[prop];
    } else {
      return globalThis[prop];
    }
  },

For some reason, this block was getting confused, and when missing property (eg. RegExp) was asked for, globalThis[prop] pointed to the same proxied object, which then recursed infinitely.
One solution was to just use target[prop] instead, however for the sake of completeness, I changed all methods to use Reflect instead, as ownKeys, defineProperty and getOwnPropertyDescriptor already did that.

I cannot come up with an explicit test-case (didnt invest much time into it yet), but so far all current tests are passing and linked issue is fixed when trying repro locally.

Fixes #17678

[kamilogorek]

One thing worth mentioning is that this issue does not occur when loading the module in-directly via createRequire, which may point in the direction of npm: specifiers doing some magic.

eg. this works just fine, even without this fix

import { createRequire } from "https://deno.land/std@0.177.0/node/module.ts";
const require = createRequire(import.meta.url);
const prettier = require("./prettier");

prettier.format('', {filename: '1.js'});

[dsherret]

On main these both go to undefined. I'm not entirely sure if this one should, but that's the current behaviour

[dsherret]

Thanks! This looks good other than the behaviour change in delete.

[kamilogorek]

Good catch, thanks! Updated

[dsherret]

LGTM. Thanks!