feat: export wp binary in package to avoid binary name conflicts

[shellscape]

This PR contains a:

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

Recent work on webpack (webpack/webpack#7534) to resolve the exported bin file names between webpack-cli and webpack-command has highlighted the inability to have both webpack-cli and webpack-command installed without conflicts that will disable one or the other (depending on install order).

While this by no means solves that dilemma, this PR proposes to add an additional bin wp (shorthand for webpack) as an export, to allow webpack-command to be used in situations where webpack-cli must also be installed.

Breaking Changes

None

Additional Info

No tests are needed for this as no code changes have been made.

Please add your thoughts to this proposal.

[shellscape]

/cc @elliottsj

[elliottsj]

I like it 👍

I would also suggest having a bin named webpack-command for extra clarity. e.g. for someone reading a package.json with

{
  "scripts": {
    "build": "wp"
  }
}

it might not be clear right away that wp maps to webpack-command.

[shellscape]

definitely not opposed to adding that, especially with the enhancements available in pnpm to take advantage of that now. hopefully a teensy bit of .bin pollution isn't negatively received.

[ematipico]

Nice addition!!