test: migrate math/base/special/hypot to ULP-based assertions

[Planeshifter]

Resolves a part of #11352.

Description

What is the purpose of this pull request?

This pull request:

• migrates test/test.js and test/test.native.js of math/base/special/hypot from relative-tolerance (EPS-based) assertions to ULP-difference assertions via @stdlib/assert/is-almost-same-value, using the minimum required ULP value.
• the only tolerance-based block in either file is the 'the function computes the hypotenuse' test, which iterates over the ./fixtures/julia/data.json fixture (2003 cases). Direct ULP-difference computation over the fixture (via @stdlib/number/float64/base/ulp-difference), using both the JavaScript implementation and a locally built native add-on, shows a maximum measured difference of 2 ULPs for both. N = 1 was confirmed to fail (16 of 2003 fixture cases), so 2 is the minimum integer bound for which all cases pass.
• the 'the function computes the hypotenuse (canonical inputs)' block and all other test blocks in both files already use exact t.strictEqual comparisons on exactly-representable values and are left unchanged, per the demonstrated idiom in the tracking issue.
• removes the now-unused EPS and abs requires and delta/tol variables.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: Migrate math/base/special packages from relative tolerance testing to ULP difference testing (tracking issue) #11352

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.

Both the JavaScript and native (test.native.js, run against a locally built add-on) test suites pass in full (2031 assertions each), run twice at the final ULP bound to confirm determinism (no FMA/arch flakiness observed).

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.".

This PR was authored by an automated Claude Code agent running as a scheduled routine: it selected an unconverted package, studied the merged prior art for this migration (e.g. math/base/special/hypotf, math/base/special/pow, math/base/special/acosh), performed the ULP-difference migration, and empirically determined the minimum ULP bound by direct measurement against the fixture data (including building and testing against a native add-on), with the bound and its determinism independently re-verified before opening this PR.

---

@stdlib-js/reviewers

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
math/base/special/hypot	$\\color{green}182/182$ $\\color{green}+100.00\\%$	$\\color{green}19/19$ $\\color{green}+100.00\\%$	$\\color{green}2/2$ $\\color{green}+100.00\\%$	$\\color{green}182/182$ $\\color{green}+100.00\\%$

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