fix(sync): validate account and slot order and boundaries in SnapProviderHelper

[Pricstas]

Fixes #XXXX

Changes

• Added validation of sorting order for accounts and storage slots in AddAccountRange and AddStorageRange
• Added boundary checks to ensure all account and slot paths fall within [startingHash, limitHash)
• Introduced new enum members to AddRangeResult: InvalidOrder and OutOfBounds

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature
• Breaking change
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: None

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Added unit tests for sorting validation in AddAccountRange and AddStorageRange.

Documentation

Requires documentation update

• Yes
• No

Requires explanation in Release Notes

• Yes
• No

[damian-orzechowski]

General question - is there a case identified to be solved or is this to address items on TODO list?

[Pricstas]

@damian-orzechowski

• Removed hard validation for boundary limits (OutOfBounds) — accounts and slots outside the range are now handled gracefully using hasExtraStorage logic.
• Kept sorting validation for accounts and slots to ensure proper boundary stitching, with comments added to clarify this behavior.
• Let me know if you'd prefer unit tests added now, or I can follow up with a separate PR.

[damian-orzechowski]

• Let me know if you'd prefer unit tests added now, or I can follow up with a separate PR.

Yes, I'd prefer to add unit test to this PR

[Pricstas]

@damian-orzechowski Added unit tests for the sorting validation as requested