chore: also run CI on fix/* and perf/* branches

[brillout]

Description

Just a small thing.

I find myself creating branches named feat/fix-* because I want the CI to be run.

Maybe we can also run the CI on fix/* branches, so that I create branches named fix/* instead of feat/fix-*.

Same for perf/*.

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[patak-dev]

Vite's test suite is getting more robust with the latest changes in the 2.9 beta. But we still get some false fails. I don't think that we gain much by duplicating the tests for fix and perf at this point. Maybe we could revisit later.

[brillout]

From Vite team's perspective, this may seem like a duplication of tests, but it isn't for the contributor: I let Vite's CI test my branch on my brillout fork of Vite, so that I know I didn't break anything before opening a PR.

Currently, if I create a branch fix/some-bug on my brillout Vite fork, the CI isn't run.

That's why I create branches named feat/fix-* so that the CI is run.

Anyways, it's just a small thing and I'm fine if we close this PR.