feat: add C implementation for stats/base/ndarray/snanmskmin

[himayurjogade]

Part of #14034.

Description

What is the purpose of this pull request?

This pull request:

• adds a C implementation for @stdlib/stats/base/ndarray/snanmskmin.
• adds a Node-API addon and tryRequire dispatcher with a fallback to the
  JavaScript implementation when the native addon is unavailable.
• adds JavaScript and C benchmarks, along with a C example.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC] : add C implementations for @stdlib/stats/base/ndarray packages (tracking issue) #14034

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request?

• The implementation follows the structure of stats/base/ndarray/dmskmax,
  which has the same two-ndarray (input + mask) signature.

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

As a first-time contributor, I used AI assistance to learn this repository's
conventions and structure, and to build this package by following the
already-merged stats/base/ndarray/dmskmax, which has an identical
two-ndarray signature. The C implementation is a thin wrapper delegating to
the existing stats/strided/snanmskmin API; the addon, tests, benchmarks, and
documentation follow that same reference throughout.

I reviewed all changes and verified them locally: the native addon compiles
without warnings, all 18 native test assertions pass with results identical to
the existing JavaScript implementation, the C example and C benchmarks run
correctly, and ESLint reports no errors.

---

@stdlib-js/reviewers

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Zulip Chat
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks