Use non-wildcard imports in mappersmith gateway

[riyadhalnur]

• Switch to using default imports for libraries imported in gateway
• Default imports (import http) create a direct reference to the module exports
• Named imports and namespace imports (import * as) create a new reference that won't reflect patches

We have a use case where we patch methods exposed by node:http and node:https globally in a node.js application. This affects applications compiled using ESM. CJS application are unaffected. Tested this change and this doesn't affect any existing applications using mappersmith.

[changeset-bot]

⚠️ No Changeset found

Latest commit: dd6bcc2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR