feat: add Fuses plugin

[erikian]

• 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:
Plugin for Fuses.

Closes #3076.

[erikian]

I had an issue where the test worked fine when running yarn test in ./packages/plugin/fuses, but failed when running the test script in the package root. After a lot of debugging, I found that adding this line from #3012 to my test fixes the issue:

forge/packages/template/typescript-webpack/test/TypeScriptWebpackTemplate_spec_slow.ts

Line 53 in af13a32

delete process.env.TS_NODE_PROJECT;

Without this line, rechoir fails to load ts-node/register with the following error, then it tries to find other .ts loaders and ultimately fails with the Unable to use specified module loaders for ".ts" error I was getting on CI:

⨯ Unable to compile TypeScript:
error TS5083: Cannot read file 'E:\Documents\Erik\forge\packages\plugin\fuses\test\fixtures\app\tsconfig.test.json'.

Also, when running the test script in the plugin folder after a previous run, it was failing with some obscure Mocha error. This was because I have "@electron-forge/plugin-fuses": "file:./../../../../fuses" in the mock app instead of something like "@electron-forge/plugin-fuses": "6.0.4", so re-running yarn install before the test was causing the issue. The solution for now is removing the node_modules folder from the mock app after finishing the test. Once the plugin is released, this will no longer be necessary.

[erikian]

Not sure if there's a better way to test unreleased plugins

[erikian]

ESLint throws a node/no-unpublished-import at me when importing some packages if they're under devDependencies, so I figured moving them to dependencies would be better than adding a bunch of es-ignore comments since it's a mock app anyway