fix: polygon query not encoding properly

[cbaker6]

New Pull Request Checklist

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

Issue Description

The withinPolygon QueryConstraint currently does not encode ParseGeoPoint's or ParsePolygon correctly.

Related issue: #380

Approach

• fix withinPolygon encoding for both ParseGeoPoint and ParsePolygon types
• Swap the latitude and longitude when encoding/decoding ParsePolygon types

TODOs before merging

• Add tests
• Add entry to changelog
• Add changes to documentation (guides, repository pages, in-code descriptions)

[parse-github-assistant]

Thanks for opening this pull request!

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

[codecov]

Codecov Report

Merging #381 (9082628) into main (926fc05) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #381      +/-   ##
==========================================
- Coverage   89.66%   89.66%   -0.01%     
==========================================
  Files         155      155              
  Lines       14123    14121       -2     
==========================================
- Hits        12663    12661       -2     
  Misses       1460     1460              

Impacted Files	Coverage Δ
Sources/ParseSwift/Types/ParsePolygon.swift	97.70% <100.00%> (ø)
Sources/ParseSwift/Types/QueryConstraint.swift	98.57% <100.00%> (-0.02%)	⬇️
Sources/ParseSwift/Objects/ParseUser.swift	86.20% <0.00%> (-0.09%)	⬇️
Sources/ParseSwift/Objects/ParseObject.swift	85.25% <0.00%> (+0.15%)	⬆️

---

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 926fc05...9082628. Read the comment docs.