refactor: remove webpack-command from CLIs

[alexander-akait]

What kind of change does this PR introduce?

refactoring

Did you add tests for your changes?

no required

Does this PR introduce a breaking change?

no

What needs to be documented once your changes are merged?

no

After merge need patch release and we archived webpack-command

[webpack-bot]

For maintainers only:

• This need to be documented (issue in webpack/webpack.js.org will be filed when merged)

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[montogeek]

A lot of other code could be refactored

[alexander-akait]

@montogeek why? It will be helpful if we have other cli in future (example experemental)

[montogeek]

@evilebottnawi Ok, sounds good

[edmorley]

Does this mean webpack-command is now no longer going to (at least for simple use cases) replace webpack-cli? From the outside it's been hard to work out which of the two is recommended / what the long term road map is...

[alexander-akait]

@edmorley long term is webpack-cli, webpack-command is will be proof of concept and many features already implemented in webpack-cli, some in WIP

[webpack-bot]

@sokra Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@ooflorent Please review the new changes.