bench: refactor to use dynamic memory allocation in blas/base/ddot

[farazghani]

Resolves a part of #8643

Description

What is the purpose of this pull request?

This pull request:

This update follows the RFC guidance for replacing patterns such as:
double x[len];
with:
double *x;
x = (double *) malloc( len * sizeof( double ) );
free( x );

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [BUG]: Segmentation fault when running C benchmarks #369

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
blas/base/ddot	$\color{green}408/408$ $color{green}+100.00%$	$\color{green}28/28$ $color{green}+100.00%$	$\color{green}4/4$ $color{green}+100.00%$	$\color{green}408/408$ $color{green}+100.00%$

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

[stdlib-bot]

⚠️ Tracking Issue Closure Warning ⚠️

I noticed your PR description contains closing keywords ("Resolves", "Closes", or "Fixes") referencing a "Tracking Issue".

Why this matters:
Tracking issues should typically remain open until all related sub-issues are completed. GitHub automatically closes issues with such closing keywords when the PR is merged. For more information, see GitHub's documentation on using keywords in issues and pull requests.

Required action:
Use "Progresses" instead to reference the tracking issue without automatically closing it.

Thank you for your contribution to the project!

[kgryte]

LGTM after clean-up. Please ensure that you have a clean Git history and your PRs are only touching a single package. Please refer to our developer guide for additional tips and tricks regarding branching.