ci: Add linter CI and lint all codes

[XMLHexagram]

Fully test on my fork. You can check https://github.com/XMLHexagram/rune/actions/runs/12126259207 .

Summary by Sourcery

CI:

• Add a new GitHub Actions workflow for linting Rust and Flutter code, including setup for toolchains and dependencies.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR adds linting configuration and CI workflows for both Rust and Flutter code. The changes include setting up GitHub Actions for code analysis, adding rustfmt configuration, and reformatting existing code to comply with Rust's formatting standards. The main focus is on code style consistency and automated quality checks.

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

File-Level Changes

Change	Details	Files
Added GitHub Actions workflow for linting	Created new linter.yml workflow file Configured separate jobs for Rust and Flutter analysis Set up dependency installation steps for both Rust and Flutter Added steps for running cargo fmt, clippy, and Flutter analyze	.github/workflows/linter.yml
Added Rust formatting configuration	Created rustfmt configuration file Configured to ignore generated message files	.rustfmt.toml
Reformatted Rust code to match style guidelines	Fixed function parameter line wrapping Adjusted indentation and line breaks Reorganized module imports Removed trailing whitespace Fixed line endings	metadata/src/reader.rs migration/src/m20230728_000008_create_media_cover_art_table.rs cli/src/main.rs database/src/actions/index.rs metadata/src/lib.rs playback/src/lib.rs playback/src/output_stream.rs analysis/src/analyzer/cpu_sub_analyzer.rs native/hub/src/sfx.rs analysis/src/analyzer/gpu_sub_analyzer.rs database/src/actions/analysis.rs database/src/connection.rs

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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 @XMLHexagram - I've reviewed your changes and they look great!

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.}

[XMLHexagram]

Well, it just works.