chore: enable integration test on windows

[LucasXu0]

Feature Preview

---

PR Checklist

• My code adheres to AppFlowy's Conventions
• I've listed at least one issue that this PR fixes in the description above.
• I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
• All existing tests are passing.

Summary by Sourcery

Extend integration testing to support Windows and macOS platforms in addition to Linux

CI:

• Update GitHub Actions workflow to add integration test jobs for Windows and macOS
• Modify flutter integration test action to support multi-platform testing with platform-specific configuration

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request enables integration tests on Windows and macOS platforms, expanding the testing coverage beyond Linux. It introduces new jobs in the CI workflow for Windows and macOS, and modifies the flutter integration test action to handle platform-specific configurations and dependencies.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Enabled integration tests for Windows and macOS in the CI workflow.	Added new jobs windows_integration_test and macos_integration_test to the workflow. Configured the jobs to run on Windows and macOS runners respectively. Defined a matrix strategy to run multiple tests in parallel on each platform. Utilized the existing flutter_integration_test action for running the tests.	.github/workflows/flutter_ci.yaml
Modified the flutter_integration_test action to support Windows and macOS.	Added conditional logic to install platform-specific prerequisites. Enabled Flutter desktop support for Windows and macOS. Added conditional logic to download artifacts based on the runner OS. Added conditional logic to run flutter tests based on the runner OS.	.github/actions/flutter_integration_test/action.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @LucasXu0 - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using a matrix strategy for the OS in the flutter_integration_test action to avoid repetition.
• The conditional artifact downloads in flutter_integration_test/action.yml seem redundant, as the action already knows the runner OS.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}