fix: Dot notation on JSON arrays doesn't work on `PushStatus` offset fields

[dplewis]

…fset fields

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

With the introduction of dot notation on array fields. https://github.com/parse-community/Parse-SDK-JS/pull/2120 doesn't include a check for PushStatus.sentPerUTCOffset and PushStatus.failedPerUTCOffset. These fields are a weird mix of dot notation, JSON arrays with numeric offset and dynamic indexes (not a zero indexed json array like the check).

This should allow merging the JS SDK to the server, https://github.com/parse-community/parse-server/pull/9128

Approach

Check for PushStatus dot notation fields

Tasks

• [x] Add tests
• [x] Add changes to documentation (guides, repository pages, code comments)

[parse-github-assistant[bot]]

Thanks for opening this pull request!

• ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (b50790a) to head (d2e8ba7). Report is 88 commits behind head on alpha.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## alpha #2194 +/- ## ========================================== Coverage 100.00% 100.00% ========================================== Files 61 64 +3 Lines 6186 6366 +180 Branches 1499 1507 +8 ========================================== + Hits 6186 6366 +180 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[parseplatformorg]

🎉 This change has been released in version 5.2.0-alpha.4

[parseplatformorg]

🎉 This change has been released in version 5.2.0-beta.2

[parseplatformorg]

🎉 This change has been released in version 5.2.0