ci(autofix): add formatting ci process

[NoiseFan]

Description

Based on @antfu/eslint-config, the formatting operation is completed when pr is submitted, and the code style is unified.

[cwandev]

Thanks for the PR! 😊

I really appreciate your contribution and the idea of adding a formatting CI process. However, after consideration, I don't think we need this right now.

Here's why:

1. We already have pre-commit hooks configured (simple-git-hooks + lint-staged) that automatically format code before commits, which covers most cases
2. Auto-committing formatting changes in CI would create extra commits that could clutter PR history
3. This would be redundant with our existing pre-commit hooks

If we start seeing formatting issues frequently in the future, we could consider adding a check-only CI workflow that fails if formatting is needed, rather than auto-fixing.

Thanks again for your contribution and understanding! 🙏

[NoiseFan]

I understand that this is a back-up measure. Some codes can be modified directly without installing dependencies. If his code style and project are not unified, this time will be even worse.

[cwandev]

I understand that this is a back-up measure. Some codes can be modified directly without installing dependencies. If his code style and project are not unified, this time will be even worse.

Thanks for your additional explanation. I understand your concerns, but I still prefer a check-only approach rather than auto-fixing. Thank you for your understanding, and I look forward to your continued participation. 😁

[NoiseFan]

Thank you for taking the time to think it over ! Hope he gets better !

[cwandev]

Hey @NoiseFan！I've changed my mind. Thanks for your patience and persistence in explaining the use case. I think your approach makes sense as a backup measure. Let me merge this PR.

[cwandev]

Thanks! @NoiseFan 👍

[NoiseFan]

Yes, the merge pull request uses square and merge, so the merge history is clean.