Validate and bound dev batch parsing in Core::set_job

[MoneroOcean]

Motivation

• Prevent malformed or attacker-controlled dev batch suffixes from being converted into unsigned values that underflow array indexes or cause unbounded memory/thread allocation.
• Address crash/OOB and resource-exhaustion risks when callers send dev values such as cpu*0, cpu*-1, or very large numbers.

Description

• Replaced atoi()-based parsing of the dev batch suffix with validated strtoul() parsing that rejects empty, non-numeric, zero, and overflowed values in moner-job.cpp.
• Added an explicit CPU-batch check to reject 0 before indexing cpu_params2variant[new_batch - 1] to avoid underflow.
• Introduced a new MAX_RX_CPU_WAYS = 32 cap and a check to bound RX batch sizes and avoid unbounded thread/memory allocation.
• Added an overflow guard that checks new_batch * new_mem_size before performing the allocation to prevent integer-overflow driven huge allocations.

Testing

• Ran npm test --silent; it failed in this environment because the native addon build cannot be completed (Unable to build node-randomx native addon), so full integration tests could not run.
• The change is isolated to Core::set_job parsing/validation logic and compiles in this workspace as a single-file change (commit recorded).

---

Codex Task