ci: Remove Release assets

[dplewis]

New Pull Request Checklist

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

Issue Description

Removes release assets from release

Closes: #1740

Approach

• Remove assets from CI
• Update README instructions

TODOs before merging

• Add tests
• 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

All modified lines are covered by tests ✅

Comparison is base (7231bf7) 78.23% compared to head (42a0f02) 64.43%.
Report is 1 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #1741       +/-   ##
===========================================
- Coverage   78.23%   64.43%   -13.81%     
===========================================
  Files         307      200      -107     
  Lines       36981    23177    -13804     
===========================================
- Hits        28931    14933    -13998     
- Misses       8050     8244      +194     

see 124 files with indirect coverage changes

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

[dplewis]

@mtrezza this is ready for review

[mtrezza]

I seem to remember that we recently did not have assets in releases and there was someone requesting they'd be added. I'm not sure about the use cases for these assets. Any good reason someone would need to add the SDK as a file directly to a Xcode project instead of using SPM?

[dplewis]

I seem to remember that we recently did not have assets in releases

Assets have been available since the beginning of the SDK.

Any good reason someone would need to add the SDK as a file directly

I'm also not sure about the use cases for these assets unless they can't get SPM to work. @parse-community/ios-sdk any idea?

[mtrezza]

Assets have been available since the beginning of the SDK.

They haven't been available at some point, I believe with the introduction with SPM. We even have added a manual CI workflow to add the assets in case the process fails. I remember there was a complaint, but I can't find it.

[mtrezza]

Let's leave this open for some days and the go ahead and remove them, I'd suggest.

[dplewis]

@mtrezza A use case is if you need to develop using an offline or static framework.

[mtrezza]

I'm continuing the discussion in #1740 (comment), because it's not PR related.

[mtrezza]

@dplewis I notice that this PR contains some changes to the README that are missing in #1744. Is this PR still useful?

[dplewis]

I’ll create another PR as there maybe merge conflicts. This PR is useful because it removes publishing the assets to GitHub on version release

[mtrezza]

Other PR: #1745