feat: allow providing properties (such as unpack) in ordering input file

[mmaietta]

Part 1 for fixing electron/universal#117

This implementation achieves proposal 2b
Excerpt below:

Bypass minimatch with more explicit control over packaging options, similar as to asar ordering logic.
b. Leverage options.ordering configuration of electron/asar to pass in stringified JSON config for each file to be unpacked

In allowing more explicit control within the ordering file, advanced usage of electron/asar is provided (and kind of needed for electron/universal's current auto-unpack logic) to bypass limitations of the minimatch package

---

Right now, the "ordering" file is simply of format:

<file path>:<anything>

Right now, electron/asar only pulls the filename value before the :

asar/src/asar.ts

Lines 92 to 95 in 121efeb

	.map((line) => {
	if (line.includes(':')) {
	line = line.split(':').pop()!;
	}

This proposal is to leverage <anything> to be JSON.stringify of Type:

{
	unpack: boolean
	// allows for future properties to be added for advanced usage without a breaking change
}

Notes:

• Retains the same logic as before for --ordering property, just extracted to a separate function
• Adds helper function to the symlinked test app "generator" to easily allow generating ordering file sets for any test that wants to leverage it.
• Taking this approach allows future configuration options to be allowed on a per-file basis should electron/asar need/desire to support more advanced usage

[felixrieseberg]

I had only one small comment, but I'm overall okay with this. Seems honestly like a good approach. I'll wait for @VerteDinde to take a look but otherwise I'm game for shipping this through!

[continuous-auth]

🎉 This PR is included in version 3.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀