Write a test to ensure configuration wizard works from e2e

We promise the user an easy onboarding experience, everything needed to do to run a WebdriverIO e2e test is to:

$ npm i @wdio/cli
$ npx wdio config --yes
$ npx wdio

We should ensure that this works all the time. There have been regressions that were unnoticed (see #5671).

Proposal

Add a CLI test in /tests/cli that:

• runs through the configuration wizard
• “fake installs” packages
• runs the test for all possible variation
  • for Mocha, Jasmine and Cucumber
  • with or without page objects
  • with or without compiler
  • additionally: run simple test with Chromedriver basic setup vs Puppeteer
• checks if they pass

The tricky part about this will be that we need to find a way to automate this without moving away from the original user experience. Here are some suggestions:

• allow to provide default answers via CLI parameters (e.g. $ npx wdio config --yes --framework jasmine would use all default values but sets jasmine as framework option)
• overwrite yarn-install dependency of @wdio/cli package to replace its functionality so that it links the packages rather than installs them from NPM (besides external packages like wdio-chromedriver-service)

[sarathps93]

I am un-assigning it so that someone else can pick it up.

[sarathps93]

Mind if I take this as my first pick?