…https.get` work when used in ESM code

The issue was that the `_wrap`ing of `http.get` was getting the
just-wrapped `http.request` by accessing `moduleExports.request`.
However, when wrapping an ES module the `moduleExports` object from IITM
is a Proxy object that allows setting a property, but *not* re-getting
that set property.

The fix is to use the wrapped `http.request` from the `this._wrap` call.
That required fixing a bug in the IITM code-path of
`InstrumentationBase.prototype._wrap` to return the wrapped property.
(The previous code was doing `return Object.defineProperty(...)`, which
returns the moduleExports, not the defined property.)

Fixes: open-telemetry#4857

…is file

Co-authored-by: Jamie Danielson <jamieedanielson@gmail.com>

Co-authored-by: Jamie Danielson <jamieedanielson@gmail.com>

Co-authored-by: Jamie Danielson <jamieedanielson@gmail.com>

Co-authored-by: Jamie Danielson <jamieedanielson@gmail.com>