fix: validate hexdump width upper bound

[skyswordw]

Summary

• cap the To Hexdump width argument at a documented maximum
• return an OperationError for oversized widths instead of surfacing a runtime RangeError
• add a regression test for the width value from Bug(To Hexdump): Uncaugh range error when Width a large number #2483

Why

A very large width value can reach String.padEnd() and throw an uncaught RangeError before CyberChef can present a normal operation error. Validating the width keeps the operation failure user-facing and bounded.

Fixes #2483.

Checks

• npm ci
• npm run lint
• npm test
• focused Hexdump operation test (13 passing)
• git diff --check

[CLAassistant]

All committers have signed the CLA.

[skyswordw]

CLA is signed now, so I am marking this ready for review.

Local checks completed before opening the PR:

• npm ci
• focused Hexdump operation tests (13 passing)
• direct oversized-width smoke check
• focused ESLint on src/core/operations/ToHexdump.mjs and tests/operations/tests/Hexdump.mjs
• full npm run lint
• full npm test (245 Node API tests and 1961 operation tests passing)
• git diff --check