fix: Updating and deleting a ParseObject sends requests even if object ID is null

[Nidal-Bakir]

New Pull Request Checklist

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

Issue Description

Closes: #828

Approach

Use assert() to make sure that the objectId is valid and can be used

TODOs before merging

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

[parse-github-assistant]

Thanks for opening this pull request!

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

[codecov]

Codecov Report

Base: 15.82% // Head: 15.78% // Decreases project coverage by -0.04% ⚠️

Coverage data is based on head (af779a2) compared to base (9ff9794).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #829      +/-   ##
==========================================
- Coverage   15.82%   15.78%   -0.04%     
==========================================
  Files          47       47              
  Lines        2876     2883       +7     
==========================================
  Hits          455      455              
- Misses       2421     2428       +7     

Impacted Files	Coverage Δ
packages/dart/lib/src/objects/parse_object.dart	14.95% <0.00%> (-0.47%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[Nidal-Bakir]

I will write the tests for these changes in my other PR.
Because I don't want to create a merge conflict.

When these changes are approved and merged into the master I will pull them to my code base and write tests for them

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[mbfakourii]

The code was tested and looks good

[mtrezza]

Since this is a fix, could you add a change log entry using the title of this PR and bump the version? It would also be great if you could add a test for the bug that is fixed here, so we can prevent this from happening in the future.

[Nidal-Bakir]

@mtrezza

It would also be great if you could add a test for the bug that is fixed here, so we can prevent this from happening in the future.

Adding tests now will create a merge conflict on my other PR.

I will add tests for this on my other PR.

I'm adding tests for every function in ParseObject class on my other PR. so adding tests for this is redundant and will make overhead for me because it will result in conflict

[mtrezza]

Got it, thanks for adding the changelog entry, let's wait for the CI and then merge this...