feat: add float16 dtype support for array/base/getter

[gururaj1512]

Resolves None

Description

What is the purpose of this pull request?

This pull request:

• feat: add float16 dtype support for array/base/getter

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

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
array/base/getter	$\\color{green}350/350$ $\\color{green}+0.00\\%$	$\\color{green}17/17$ $\\color{green}+0.00\\%$	$\\color{green}13/13$ $\\color{green}+0.00\\%$	$\\color{green}350/350$ $\\color{green}+0.00\\%$

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

[kgryte]

LGTM after clean-up. @gururaj1512 Please make sure you are investigating lint failures. Yes, for some of your work, such as in the plot refactor, we effectively ignore, but all failures should be investigated regardless in order to eliminate the possibility of human error. If you don't, just requires additional clean-up and increases the likelihood of bugs.