MOD-4107 Limit json doc depth to 128

[AvivDavid23]

Note

Imposes a strict depth cap to prevent excessively nested JSON values.

• Introduces MAX_DEPTH=128 and SelectValue::calculate_value_depth(); tracks traversal depth in follow_path
• Propagates depth to mutators and enforces limits in set_value, dict_add, arr_append, arr_insert, and merge via can_merge() with err_recursion_limit_exceeded
• Publicizes error helpers and uses bounded parsing for RDB load (from_str(..., limit_depth=true))
• Adjusts APIs to pass depth (closures now receive usize depth)
• Updates tests: remove unbounded-depth cases; add coverage for depth limits in JSON.SET/MSET, array ops, and JSON.MERGE

^{Written by Cursor Bugbot for commit 77954da. This will update automatically on new commits. Configure here.}

[codecov]

Codecov Report

❌ Patch coverage is 95.83333% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 77.82%. Comparing base (de7a14e) to head (77954da).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
redis_json/src/ivalue_manager.rs	94.52%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1487      +/-   ##
==========================================
+ Coverage   77.55%   77.82%   +0.27%     
==========================================
  Files          15       15              
  Lines        3832     3897      +65     
==========================================
+ Hits         2972     3033      +61     
- Misses        860      864       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

[gabsow]

mybe this is too costy in terms of prefomence