docs: Fix jazzy undocumented symbols

[dplewis]

New Pull Request Checklist

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

Issue Description

There are a lot of errors when generating docs that prevents symbols from being documented.
https://github.com/parse-community/Parse-SDK-iOS-OSX/actions/runs/11596782336/job/32288646411

error: 'BFTask.h' file not found
error: module 'Bolts' not found

Before

After

Approach

• Move @import Bolts to .m and add @class to .h
• Remove duplicate properties like dataAvailable from catetories
• Add missing imports for Constants
• Properly handle Bolts import
• Remove old carthage/pods imports
• Remove console errors

TODOs before merging

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

[parse-github-assistant]

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]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.79%. Comparing base (dd05d41) to head (ac4eafd).
Report is 29 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #1820       +/-   ##
===========================================
+ Coverage   64.24%   82.79%   +18.55%     
===========================================
  Files         201      282       +81     
  Lines       23233    30726     +7493     
===========================================
+ Hits        14926    25441    +10515     
+ Misses       8307     5285     -3022     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mtrezza]

Why are the tests failing

[dplewis]

@mtrezza For some reason functions that return BFTask can't be called in swift after this change.

+ (nonnull BFTask<NSNumber *> *)trackEvent:(nonnull NSString *)name;

class func trackEvent(_ name: String) -> BFTask

[mtrezza]

I also wanted to say that there a quite a few changes in code so not sure if that can be considered "only " a docs PR?

[dplewis]

@mtrezza I found a cleaner way to do this, simple refactoring. I think the build is broken too

[mtrezza]

The build worked in the PR last week, so I assume it's this PR that breaks it?

[dplewis]

All my PR’s have flaky test introduced, simulators we use aren’t available anymore in certain version of Xcode, I don’t know if it’s a github action issue

[mtrezza]

Not sure I understand; the CI currently passes, see for example https://github.com/parse-community/Parse-SDK-iOS-OSX/actions/runs/11758150963. All jobs passed at first run, but to be sure, I've restarted the CI for another run to see if there is any flakiness. I've restarted the CI here too, so we can compare the errors between the two runs.

[mtrezza]

Turns out the CI is also flaky in that other PR. So I'll just rerun the CI here until hopefully all pass.

[mtrezza]

@dplewis I couldn't get the CI to pass, even after re-running the failed tests multiple times. What should we do here?

[dplewis]

I closed this because it introduces a breaking change when using this SDK in a swift environment. Can you do a release PR? The Xcode 16 support got added. If that PR has flaky test then I don’t know what to do but as least we can investigate

[mtrezza]

Are the changes in 0be6870 necessary to use the SDK in Xcode 16? I assumed it only added the Xcode 16 tests to the CI and the gemfile dependency upgrades were done additionally but not required for Xcode 16. Hence this wasn't merged as feature release.

[dplewis]

Just a suggestion if you want to update the change log then a release would be nice. A patch release would work as no functionality has changed.

[mtrezza]

I think you are right, that should have been merged as feat, not as ci. Let me see how I can trigger a release here. Opened #1823.