fix: validate pagination params in memory tools

[ZayanKhan-12]

Summary

The pagination params in src/tools/memory.ts were declared as plain zod.number().optional(), while the equivalent params in console.ts and network.ts use stricter schemas (.int().positive() for pageSize, .int().min(0) for pageIdx).

Because of the laxer schemas, invalid values reached paginate() in src/utils/pagination.ts:

• pageSize: 0 produces totalPages: Infinity (Math.ceil(total / 0)) with an empty items array
• negative or fractional pageSize slices nonsensical ranges

This PR aligns all five paginated memory tools (get_heapsnapshot_details, get_heapsnapshot_class_nodes, get_heapsnapshot_retainers, get_heapsnapshot_edges, get_heapsnapshot_duplicate_strings) with the console/network schema pattern, including the describe() wording, so invalid values are rejected at the schema layer with a clear validation error instead of producing broken pagination output.

docs/tool-reference.md and src/bin/chrome-devtools-cli-options.ts are regenerated via npm run gen.

This inconsistency was noticed while writing pagination tests in #2510.

Changes

• src/tools/memory.ts: pageSize → zod.number().int().positive().optional(), pageIdx → zod.number().int().min(0).optional() for all paginated memory tools
• tests/tools/memory.test.ts: new pagination schemas tests asserting that 0, -1, and non-integer values are rejected and valid values still parse
• docs/tool-reference.md, src/bin/chrome-devtools-cli-options.ts: regenerated

Testing

• npm run build — passes
• npm run gen — regenerated docs/CLI options, no unexpected diffs
• node scripts/test.js tests/tools/memory.test.ts — passes, including the new schema-rejection tests
• npm run test:no-build — full suite passes (exit 0)
• npm run check-format — clean

🤖 Generated with Claude Code

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Lightning00Blade]

LGTM, let's remove the test as we are testing as it test a library not our code.

[Lightning00Blade]

This test technically tests the zod, so we can remove it.