ci: add Biome code quality workflow and upgrade to v2.1.3

[kangju2000]

• Add GitHub Actions workflow for automated Biome code quality checks
• Upgrade Biome to v2.1.3 with updated configuration
• Update VS Code settings for improved development experience

[gemini-code-assist]

Summary of Changes

Hello @kangju2000, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing our project's code quality infrastructure by upgrading Biome to its latest version and refining its configuration. It also improves the local development experience by updating VS Code settings to better integrate with Biome's formatting and linting capabilities. The overall goal is to ensure consistent code style and quality across the codebase, preparing for automated checks in CI.

Highlights

• Biome Version Upgrade: I've upgraded the Biome code quality tool from version 2.0.6 to 2.1.3 by updating the package.json and pnpm-lock.yaml files. This ensures we're using the latest features and fixes from Biome.
• Biome Configuration Updates: The biome.json configuration has been updated to reflect the new version and enhance its functionality. I've enabled VCS integration to respect .gitignore files, added an exclusion for drizzle related files from Biome processing, and turned off the noUselessConstructor linter rule under complexity.
• VS Code Editor Settings: I've refined the VS Code settings in .vscode/settings.json to improve the development experience with Biome. Specifically, source.fixAll is now set to explicit instead of always for more controlled automatic fixes, and Biome is now configured as the default formatter for typescriptreact files.
• CI Workflow Integration (Implied): While the GitHub Actions workflow file itself isn't part of this patch, the PR title and description indicate that a new CI workflow for automated Biome checks is being added. This PR lays the groundwork by updating Biome and its configuration, which would be consumed by such a workflow.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to add a Biome CI workflow and upgrade the dependency. The upgrade and configuration changes look good. However, the main piece, the GitHub Actions workflow file mentioned in the title and description, seems to be missing from the changes. Please add it to the PR.

I've also added a couple of suggestions to the biome.json file to improve its clarity and maintainability.