integrate init command with CLI by default

[rishabh3112]

Is your feature request related to a problem? Please describe.
As part of roadmap, we like to integrate init by default.
This is the tracker issue and discussion thread for this work.

Describe the solution you'd like

• Robust tests for init's current features - completed - tests: add more tests for init #1508, tests: add tests for init #1419
• Refactor init and add/remove features from it - completed - feat(init): add features and refactor #1590
  - Add flag to force configuration generation.
• Add tests for the previous step changes (if any) - completed - feat(init): add features and refactor #1590
• Integrate it with CLI - completed - feat: add init to webpack-cli #1609
• Add integration tests for verifying integration, - completed - feat: add init to webpack-cli #1609

Describe alternatives you've considered
N/A

Additional context
Roadmap #717

/cc @evilebottnawi

[alexander-akait]

Yes, good job 👍

One strange thing - init command doesn't generate config by default, I think main purpose init is to generate config + additional commands to improve it

[rishabh3112]

It is 0CJS by default. Anytime a situation can be handled by defaults, configuration is not generated.

It gets generated when we need something like CSS preprocessors, etc.

Would add a test for that in the PR I have sent for init tests. #1508

[alexander-akait]

@rishabh3112 Agree, but sometimes you really need integrate configuration, so will be great have flag for this

[rishabh3112]

Okay, lets do it in the second step in above list.

[rishabh3112]

Completed, closing the issue now 😀