fix(template): bump react-swc plugin version

[ArnaudBarre]

Some users have been hit by pnpm/pnpm#6463

I think we should reconsider the usage of pnpm create in docs because plugins evolves more than the published templates (cc @patak-dev)

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[patak-dev]

I think we should reconsider the usage of pnpm create in docs because plugins evolves more than the published templates (cc @patak-dev)

Do you have an idea to solve this issue? I think pnpm was going to start auto-upgrading to the latest version in range when there wasn't a lock, no? If that is the case, users should get the latest minor and for majors it makes sense we check first 🤔
Maybe we could automate receiving a PR when there is a major in a plugin?

[ArnaudBarre]

The PR is stale because from what I understand they want to touch the package.json when doing so, which I also found bad.
I don't see why installing latest version on no lockfile but wihtout touching package.json (like every other package and manager and what did pnpm before) is not possible.

[patak-dev]

I agree there. I think Svelte added a .npmrc to all their templates. Maybe we should do that? cc @dominikg. We already waited quite a bit here. What I dislike is that all our templates will end up with a non-default pnpm setup moving forward if we go there, but maybe it could work as a temporary solution.