feat: add support for forge.config.ts et. al

[MarshallOfSound]

This brings in rechoir and interpret which allow arbitrary extensions / loaders for our forge config.

Notably this allows us to make forge.config.ts a thing (and thus generate type safe configurations).

This also splits our ForgeConfig type into two types ForgeConfig and ResolvedForgeConfig.

• ForgeConfig is the partial config definition that a user provides
• ResolvedForgeConfig is the full config that is passed around internally and populated with defaults

This was done so that ForgeConfig could be used by apps for their config files. E.g.

import { ForgeConfig } from '@electron-forge/shared-types';

const config: ForgeConfig = {
  // config goes here
};

export default config;

[codecov]

Codecov Report

Merging #2993 (493368c) into main (493368c) will not change coverage.
The diff coverage is n/a.

❗ Current head 493368c differs from pull request most recent head cc9df7f. Consider uploading reports for the commit cc9df7f to get more accurate results

@@           Coverage Diff           @@
##             main    #2993   +/-   ##
=======================================
  Coverage   74.19%   74.19%           
=======================================
  Files          67       67           
  Lines        2178     2178           
  Branches      436      436           
=======================================
  Hits         1616     1616           
  Misses        355      355           
  Partials      207      207           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 493368c...cc9df7f. Read the comment docs.

[VerteDinde]

Since we've been working on docs, would it be helpful to also have an example of a forge.config.ts that users could reference? That might be nice to create while it's top of mind

[MarshallOfSound]

Since we've been working on docs, would it be helpful to also have an example of a forge.config.ts that users could reference? That might be nice to create while it's top of mind

My plan was to do that and change the webpack-typescript template to use forge.config.ts once this lands

[SpacingBat3]

FYI, this was actually a thing in my project even before it made it there. You might find that interesting as an example how I did that previously (and how it was possible to do so) and probably continue doing that.

I had to patch some internal types through, to get more accurate types when comparing it with Electron Forge documentation.