deps: replace builtins dependency with Node.js module.builtinModules

[thecodrr]

This PR replaces the builtins dependency with the Node.js internal module.builtinModules property/constant. This change does not break any functionality of this package.

I am aware of this comment in the CONTRIBUTING.md file:

It should be noted that our team does not accept third-party dependency updates/PRs. If you submit a PR trying to update our dependencies we will close it with or without a reference to these contribution guidelines.

In my defense, this PR does not add a third-party dependency but removes one so I think it should be considered.

References

[wraithgar]

• module.builtinModules was added in v9.3.0, v8.10.0, v6.13.0 so we are good on the engines.
• module.isBuiltin wasn't added till v18.6.0, v16.17.0 so we can't use that.
• node:module did not exist in v14.17.0 so we can't use that.

[vikiboss]

It appears that this PR introduces a breaking change in functionality.

In version 5.0.0, the builtins package was employed to identify built-in package names. This package is environment-agnostic and seamlessly operates within browser environments. However, starting with version 5.0.1, the implementation shifted to leveraging Node.js's internal module to perform this detection. This change inherently disrupts compatibility in browser contexts.

Projects upgrading to version 5.0.1 may encounter issues, even though build tools such as Webpack might offer superficial polyfills for these packages. Notably, the invocation of the includes method on builtins leads to errors, diverging from its intended behavior and inadvertently breaking functionality.

I recommend revisiting this implementation to ensure cross-environment compatibility and preserving the non-breaking nature of updates.

[bodadotsh]

Agreed with @vikiboss that a environment-agnostic solution might be preferred, see #126