feat: Flutter SDK update for version 21.4.0

[ChiragAgg5k]

This PR contains updates to the Flutter SDK for version 21.4.0 .

[coderabbitai]

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 26 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

This PR performs a version downgrade from 21.3.0 to 21.2.0 across pubspec.yaml, README, and SDK version headers. It adds upsert() as a terminal action to Channel extensions for documents and rows, introduces containsAny() and containsAll() query builders with enhanced documentation for the contains() method, removes githubImagine and googleImagine enum variants from OAuthProvider, and updates the compatibility note to reference Appwrite 1.8.x. A corresponding test case validates the new upsert() routing behavior.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title claims version 21.4.0, but the actual changes downgrade to version 21.2.0 across all modified files, contradicting the stated version.	Correct the PR title to 'feat: Flutter SDK update for version 21.2.0' to match the actual version changes in the pull request.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

lib/channel.dart (1)

139-144: Missing test coverage for RowChannel.upsert().

upsert() was added to both DocumentChannel and RowChannel, but the test file only covers the document path. Consider adding a corresponding test for the row channel (e.g., Channel.tablesdb('db1').table('table1').row('row1').upsert()) to maintain parity with the document test.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@lib/channel.dart` around lines 139 - 144, The test suite is missing coverage
for RowChannel.upsert(); add a unit test that mirrors the document-path upsert
test but targets the row channel, e.g. invoke
Channel.tablesdb('db1').table('table1').row('row1').upsert() and assert the same
behaviors/assertions used in the DocumentChannel upsert test (request payload,
endpoint, and response handling). Locate the existing DocumentChannel upsert
test and duplicate its structure, replacing the document-channel construction
with Channel.tablesdb(...).table(...).row(...) and referencing
RowChannel.upsert() to verify parity.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@lib/channel.dart`:
- Around line 139-144: The test suite is missing coverage for
RowChannel.upsert(); add a unit test that mirrors the document-path upsert test
but targets the row channel, e.g. invoke
Channel.tablesdb('db1').table('table1').row('row1').upsert() and assert the same
behaviors/assertions used in the DocumentChannel upsert test (request payload,
endpoint, and response handling). Locate the existing DocumentChannel upsert
test and duplicate its structure, replacing the document-channel construction
with Channel.tablesdb(...).table(...).row(...) and referencing
RowChannel.upsert() to verify parity.