Clamp sprite limit inputs to prevent OOB and exhaustion

[segrax]

Motivation

• The code made mSpritesMax externally controllable (CLI/INI/demo JSON) while many engine paths still assume at least 45 sprites, allowing out-of-bounds writes and memory-exhaustion via crafted inputs.\
• Introduce a minimal, centralized validation to prevent malicious or accidental underflow/overflow of the sprite vector while preserving original defaults.

Description

• Added MIN_SPRITES_MAX = 45 and MAX_SPRITES_MAX = 100000 constants to sFodderParameters in Source/Parameters.hpp to centralize safe bounds.\
• Tied CUSTOM_DEFAULT_MAX_SPRITES to the new MAX_SPRITES_MAX to keep custom-mode defaults consistent in Source/Parameters.cpp.\
• Clamped mSpritesMax to the [MIN_SPRITES_MAX, MAX_SPRITES_MAX] range when loading from demo/save JSON in sFodderParameters::FromJson.\
• Clamped mSpritesMax after parsing CLI (--max-sprite) in sFodderParameters::ProcessCLI and after reading engine.maxsprite from openfodder.ini in sFodderParameters::ProcessINI to cover all untrusted input paths.\

Testing

• No unit tests were executed for this change.\
• Performed automated code searches with rg to verify all input code paths (mSpritesMax, --max-sprite, Sprite_Clear_All, Map_Load_Sprites) are covered by the clamping changes and inspected diffs with git diff, which succeeded.\
• Changes were committed successfully with the message Clamp max sprite parameter to safe range.

---

Codex Task