fix: Incorrect type in ParseObject.fetch parameter options

[swittk]

Pull Request

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

Issue

FetchOptions should be an optional parameter same as before the V6 changes. The ObjectController downstream already handles this parameter as optional.

Closes: #2725

Approach

Adds the optionality to the typescript type.

Tasks

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

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[parseplatformorg]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (6941012) to head (47d7f21).

Additional details and impacted files

@@            Coverage Diff            @@
##             alpha     #2726   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           63        63           
  Lines         6185      6185           
  Branches      1472      1456   -16     
=========================================
  Hits          6185      6185           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mtrezza]

Could you please take a look at https://github.com/parse-community/Parse-SDK-JS/blob/alpha/CONTRIBUTING.md#typescript-tests for type modifications to fix the failing test.