feat: add assert/has-promise-support

[0PrashantYadav0]

Resolves None

Description

What is the purpose of this pull request?

This pull request:

• Introduces a new module that checks for native Promise support in the environment. The module exports a function that returns a boolean indicating the presence of Promise support.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• None.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
assert/has-promise-support	$\\color{green}116/116$ $\\color{green}+0.00\\%$	$\\color{red}6/7$ $\\color{green}+0.00\\%$	$\\color{green}1/1$ $\\color{green}+0.00\\%$	$\\color{green}116/116$ $\\color{green}+0.00\\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

Left initial comments.

[0PrashantYadav0]

Thanks for the feedback and Yes, the current check was too shallow and didn't follow the feature-detection pattern used elsewhere (e.g. has-map-support): capturing the global once in a dedicated module, then validating the constructor plus the original Promise.resolve / Promise.reject statics, without any async work. I'll update lib/main.js accordingly and expand the tests with proxyquire to cover both positive and negative mocks.

[0PrashantYadav0]

In last commit :

• Updated the hasPromiseSupport function to check for the presence of resolve and reject methods on a custom GlobalPromise module.
• Introduced a new promise.js module to encapsulate the Promise constructor.
• Expanded tests to include mocked scenarios for promise support detection, ensuring accurate results for both supported and unsupported cases.

[kgryte]

LGTM after clean-up.