chore(pnpm-workspace.yaml): packages/* in the pnpm-workspace.yaml is vague, it would be better to list specific package names

[peterlevel1]

Purpose: Better for managing packages of vuejs/core

As vuejs/core project grows, it would be better to list specific package names, which can be more clear to see how many packages in the project when using pnpm as package manager.

Why this commit ?

An error shown when running pnpm build:
../packages/reactivity-transform/package.json is not found

Above error gave me a confusing for a short time, and after comparing the remote vuejs/core code repo with local code base, making sure this empty folder should not be appear in the project.

Benefits

If the specific package name listed in the pnpm-workspace.yaml, there would be 2 benefits apparently

1. More clear when adding package

Adding package would be more clear in the project, as it must be handled by pnpm in the pnpm-workspace.yaml

2. Packages reference

As packages reference for folders in the packages, which holding so many packages in the vuejs/core project that pnpm-workspace.yaml file can be compared with existed packages in the packages folder.

[yyx990803]

I don't think I agree. All directories under packages should be treated as a workspace package by pnpm to ensure correct dependencies. Manually listing them only creates room for error in the future (e.g. creating a new package without adding them to the workspace), and this would already require changes to core-vapor which adds a bunch of new packages.

reactivity-transform was removed in the 3.4 release and it's a leftover due to the lingering files not checked into git and thus preserved by git when checking out the newer commit.

[peterlevel1]

Ok, agree