feat: improve the build using rollup

[mato533]

Description

To avoid complications of ESM and CJS build, Implement rollup as bundler.

We created new package @wdio/electron-bundler because there are some logic to create rollup configurations.
This could be achieved by simply creating a common configuration file and use from each package, but we packaged it to improve the quality of the entire library by introducing a unit test for the logic that creates the rollup configuration itself.

Core motivation

we have to set aligned value between output.dir of the rollup option and out Dir of the typescript option.

Specifically, the path of typescript compiler option 'outdir' must be located inside rollup 'dir' option.

To create a library that supports both CJS and ESM, the source code for each format needs to be stored in separate directories.(when not use cjs,mjs) This means different paths must be specified for output.dir in the Rollup configuration.

So, new package is created to genelate the rollup programmatically.
＊) related info

Feature

1. The input parameter is automatically created based on exports field of package,json
   Reduce the effort of synchronizing package.json settings and Rollup settings.

2. Create parameters that enable ESM and CJS style output.

3. Synchronizes @rollup-plugin-typescript settings with rollup settings and enables output of *.d.ts files.

Related Issue

#880

@goosewobbler
Since this is a major modification, I would appreciate it if you could give me your frank opinions on whether or not to create a new package, and on the following structural changes for dist.

[goosewobbler]

I think extracting the rollup configs and having another package is ok, I would call it @wdio/electron-bundler - however, there's a lot of code here simply to create rollup config files. I think a simpler approach would be better, I will take a look at it in more depth over the holiday...

[mato533]

@goosewobbler
thank you for your review.
your thoughts that is too much source code is understandable for me....

The part what increases the amount of source code is following functionality.

• Determination for input option of rollup based on read exports field of package.json (related code)

• Determination for output option of rollup based on read main , module field of package.json

  • If it will be determined that maintained manually or fixed value, as a result we can reduce the code. (related code)

• some option parameter is existing that is not required for now (related code)

  • it has been removed. but plugin options are remains because it can only be set at generation time.