pnpm --filter seems to pass the filter argument to all the sub-commands

[bligneri]

I just updated to pnpm 9.4.0 and I noticed something new.

It seems that the whole --filter arguments are passed to every subsequent commands
It broke my local build as well as CI/CD.

For instance on a github worker:

```#20 6.803  ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  @prismaCleanData/[email protected] build: `prisma generate "--filter=my-app..."````

Locally: with the --filter=@repo/lib argument:

packages/lib build$ tsc "--filter=@repo/lib"
packages/lib build: error TS5023: Unknown compiler option '--filter=@repo/lib'.
packages/lib build: Failed
/Users/ben/Src/ESA/monorepo/packages/lib:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  @repo/[email protected] build: `tsc "--filter=@repo/lib"`
Exit status 1
 ELIFECYCLE  Command failed with exit code 1.
 ```
 
 As we can see, it seems that the `--filter my-nice-filter...` argument is passed to every subsequent command.
 
 I don't think this should be the default behaviour as it would require every command to accept this option.

[bligneri]

OK. I think I understand.

so pnpm --filter=my-nice-filter... build works.
While pnpm build --filter=my-nice-filter... does not and propagate everything after the command to all the subcommands.

It makes sense ;-)