Add public API

[malept]

As it currently stands, Electron Forge is CLI driven. If you want to interact with it in another Node module, you need to shell out. In order to better integrate with solutions such as ember-electron, we should refactor the logic so that it's accessible via a public (documented) API.

[MarshallOfSound]

As briefly mentioned in slack I think the easiest way to make this work is

• Extract all actual logic in all the "main" async functions to their own files in a new folder "api"
• Make these functions take in a single options parameter with the same property names as the "program" object.
• Add another property to all options objects interactive which defaults to false and would disable ora and inquirer (so that when you use the API we don't flood their console)
• Set the main file of electron-forge to export all the commands as named constants so that users can simply

import { lint, make, publish } from 'electron-forge';

/cc @felixrieseberg

[MarshallOfSound]

The one thing I really want to avoid is maintaining two separate interfaces for electron-forge, we just be first party consumers of the "API" ourselves to avoid this happening.