[Bug]: yarn create doesn't work with @scope

[alan-agius4]

Self-service

• I'd be willing to implement a fix

Describe the bug

When using yarn create the version specifier doesn't work when the package is scoped. Example yarn create @angular@next.

 YN0000: ┌ Resolution step
➤ YN0001: │ Error: create-@angular@next isn't supported by any available resolver
    at Bd.getResolverByDescriptor (/.node/corepack/yarn/3.2.1/yarn.js:396:1664)
    at Bd.bindDescriptor (/.node/corepack/yarn/3.2.1/yarn.js:396:1053)
    at ee (/.node/corepack/yarn/3.2.1/yarn.js:442:6954)

To reproduce

yarn create @angular@next

Environment

System:
    OS: Linux 5.17 Debian GNU/Linux rodete 12 (rodete)
    CPU: (48) x64 AMD EPYC 7B12
  Binaries:
    Node: 16.15.1 - /tmp/xfs-cbdcc8f4/node
    Yarn: 3.2.1 - /tmp/xfs-cbdcc8f4/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm

Additional context

No response

[merceyz]

I see npm documents

npm init <@scope> (same as `npx <@scope>/create`)

so I'll add support for that as well.

Though note it doesn't actually work with npm

$ npm init @angular@next
npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name "@angular" of package "@angular@next/create": name can only contain URL-friendly characters.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-07-15T16_07_31_388Z-debug-0.log

[alan-agius4]

@merceyz, yeah I am aware of that. I have a separate issue for that npm/cli#5175