feat: add ndarray/base/shift

[headlessNode]

---

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: passed
• 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: na
• task: lint_c_examples status: na
• 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: passed
• task: lint_license_headers status: passed ---

Resolves stdlib-js/metr-issue-tracker#87.

Description

What is the purpose of this pull request?

This pull request:

• add ndarray/base/shift

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves [RFC]: add ndarray/base/shift metr-issue-tracker#87
• progresses [RFC]: achieve ndarray API parity with built-in JavaScript arrays  #2656

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
ndarray/base/shift	$\color{green}160/160$ $\color{green}+100.00\%$	$\color{green}7/7$ $\color{green}+100.00\%$	$\color{green}1/1$ $\color{green}+100.00\%$	$\color{green}160/160$ $\color{green}+100.00\%$

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

[kgryte]

@headlessNode I ended up making a number of changes in #8108 that we'll want to incorporate in this PR.

One of the biggest changes is the removal of the strict argument, which doesn't make sense for pop and shift. That argument makes sense for the slice* APIs because a user provides one or more slice arguments. And it is those arguments that the strict argument applies to.

Furthermore, I added explicit error handling for dimension normalization. As discussed elsewhere, we already do this in other very similar base APIs (e.g., slice-dimension-to, slice-dimension-from) and there isn't much a reason why pop and shift should deviate.