fix: Query conditions `inQuery` and `notInQuery` not working properly

[mbfakourii]

New Pull Request Checklist

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

Issue Description

There was an unused "," value in the _buildQueryRelational function

Closes: #849

Approach

n/a

TODOs before merging

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

[parse-github-assistant[bot]]

Thanks for opening this pull request!

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

[codecov[bot]]

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d1b07fe). Click here to learn what that means. Patch coverage: 100.00% of modified lines in pull request are covered.

:exclamation: Current head 934a090 differs from pull request most recent head 98a24cd. Consider uploading reports for the commit 98a24cd to get more accurate results

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #869 +/- ## ========================================= Coverage ? 39.13% ========================================= Files ? 56 Lines ? 3278 Branches ? 0 ========================================= Hits ? 1283 Misses ? 1995 Partials ? 0 ``` | [Impacted Files](https://app.codecov.io/gh/parse-community/Parse-SDK-Flutter/pull/869?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=parse-community) | Coverage Δ | | |---|---|---| | [packages/dart/lib/src/network/parse\_query.dart](https://app.codecov.io/gh/parse-community/Parse-SDK-Flutter/pull/869?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=parse-community#diff-cGFja2FnZXMvZGFydC9saWIvc3JjL25ldHdvcmsvcGFyc2VfcXVlcnkuZGFydA==) | `32.42% <100.00%> (ø)` | |

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[mtrezza]

Is this ready for review?

[mbfakourii]

Is this ready for review?

Yes, it is ready for review

[Nidal-Bakir]

Can you add a test to ensure that this does not happen again?

[mbfakourii]

Can you add a test to ensure that this does not happen again?

Yes, sure

[mbfakourii]

@mtrezza Why did half of the CI failed?

[Nidal-Bakir]

Why did half of the CI failed?

See https://github.com/parse-community/Parse-SDK-Flutter/pull/874 and https://github.com/parse-community/Parse-SDK-Flutter/issues/872#issuecomment-1544985663

[mbfakourii]

Looks good, could you just rephrase the PR title, it seems to describe the technical solution instead of the bug that is fixed by this PR; so that we have a meaningful changelog entry

I changed The problem is very small. I don't have a better idea for the title

[mbfakourii]

Could you add a changelog entry?

added