deps: fix webpack dependency

[rtritto]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• The changes are appropriately documented (if applicable).
• The changes have sufficient test coverage (if applicable).
• The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:

• In @electron-forge/plugin-webpack dependency move webpack to peer dependencies
• In @electron-forge/template-webpack-typescript dependency add webpack dependency (transitive peer dependency of @electron-forge/plugin-webpack)

Fix #3695

[rtritto]

FYI @MarshallOfSound

[VerteDinde]

Why do we need webpack as a peerDependency here?

[rtritto]

fork-ts-checker-webpack-plugin use webpack (peer dependency) imply that webpack is auto installed by package manager as transitive peer depenedncy.
All transitive peer dependencies must be used as dependencies or peer dependencies.
An article written by author of yarn package manager: Implicit Transitive Peer Dependencies

webpack can be added once because it's a peer dependency.

[MarshallOfSound]

This isn't right, the plugin needs to have full control of the webpack version, not just set it correctly once when the template installs.

[rtritto]

Maybe fork-ts-checker-webpack-plugin should use webpack as @electron-forge/plugin-webpack:

// packages/template/webpack-typescript/package.json and packages/template/webpack-typescript/tmpl/package.json
"devDependencies": {
  "webpack": "npm:@electron-forge/plugin-webpack@^7.4.0"
}