feat: add C ndarray interface and refactor implementation for stats/base/dstdev

[gururaj1512]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: passed
• task: lint_package_json status: na
• task: lint_repl_help status: passed
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: passed
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: missing_dependencies
• task: lint_c_examples status: missing_dependencies
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

Resolves None

Description

What is the purpose of this pull request?

This pull request:

• adds C ndarray interface for stats/base/dstdev
• refactors JavaScript implementation
• refactors tests, docs, benchmarks and examples.

Related Issues

Does this pull request have any related issues?

This pull request:

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

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/base/dstdev	$\color{green}348/348$ $\color{green}+100.00\%$	$\color{green}13/13$ $\color{green}+100.00\%$	$\color{green}4/4$ $\color{green}+100.00\%$	$\color{green}348/348$ $\color{green}+100.00\%$

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

[0PrashantYadav0]

@gururaj1512 we already have pr doing same #4685

[kgryte]

@0PrashantYadav0 Indeed. This is a duplicate PR; however, that one still has merge conflicts and this one is ready to go, so let's go ahead and merge this one and close the other.

[kgryte]

@gururaj1512 As a general practice, be sure to check the PR queue to determine if an existing PR already exists and whether it can be salvaged, in order to avoid duplicate work. Thanks!

[gururaj1512]

@gururaj1512 As a general practice, be sure to check the PR queue to determine if an existing PR already exists and whether it can be salvaged, in order to avoid duplicate work. Thanks!

Sure