fix: always sort JSON encoded keys

[cbaker6]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

When using the SDK encoders, the keys are not required to be sorted. Since a JSON encoded string is sometimes used a keys or compared directly internally, it can lead to matches not found when saving ParseObject's that have children ParseObect's.

This is also the reason why multiple tests are disabled for Linux and Windows.

Related issue: #n/a

Approach

Make all SDK encoders sort keys.

TODOs before merging

• Modified tests for changes
• Enabled 110+ more tests for Linux & Windows
• Add entry to changelog

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[codecov]

Codecov Report

Merging #318 (f4fb9b7) into main (b2a0d9c) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #318      +/-   ##
==========================================
+ Coverage   84.66%   84.70%   +0.04%     
==========================================
  Files         114      114              
  Lines       11845    11850       +5     
==========================================
+ Hits        10028    10037       +9     
+ Misses       1817     1813       -4     

Impacted Files	Coverage Δ
Sources/ParseSwift/Coding/ParseCoding.swift	88.15% <100.00%> (+0.15%)	⬆️
Sources/ParseSwift/Coding/ParseEncoder.swift	74.35% <100.00%> (+0.12%)	⬆️
Sources/ParseSwift/LiveQuery/ParseLiveQuery.swift	73.66% <0.00%> (+0.14%)	⬆️
Sources/ParseSwift/Objects/ParseObject.swift	81.94% <0.00%> (+0.47%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b2a0d9c...f4fb9b7. Read the comment docs.