feat: Add ignoreOrder flag

[mjhenkes]

This PR contains a:

• bugfix
• new feature
• code refactor
• test update
• typo fix
• metadata update

Motivation / Use-Case

Picking up the torch where #366 left off and making the changes suggested by @evilebottnawi
Also addresses #362
Borrowing @hedgepigdaniel 's description:

As has been pointed out in #250:

• Sorting all imports (not just in files but in tree traversal import order is difficult to do in a large project, and impossible if there are async chunks with CSS.
• Consistent use of scoping or naming conventions in CSS makes the order of CSS import irrelevant, and this is a much more manageable strategy for a large project as @jsg2021 said in New version 0.4.2 capture lot of warnings #250 (comment)
• Using stats.warningFilter as recommended by @sokra in New version 0.4.2 capture lot of warnings #250 (comment) or webpack-filter-warnings-plugin does not work consistently. It's much better to avoid generating the warnings at their source (optionally) rather than to partially filter them later with regexes. For example, I use webpack-error-on-warnings-plugin to enforce that there are no warnings in a build. This is incompatible with filtering warnings, because it the error must happen in the before-emit hook so that it prevents emission of assets when there are warnings. The warnings filtering happens in the done hook or in the toJson method, which is too late.

Breaking Changes

None

Additional Info

The added tests is to ensure that enabling the flag doesn't make the plugin implode, but it doesn't really programmatically verify the warnings aren't printed.

fixes #362

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

[kubijo]

Can someone from mainteiners merge this please.
The code seems nice, terse and without conflicts, so this should be a quick pass-over

[alexander-akait]

Please add test with ignoreOrder: false

[mjhenkes]

@evilebottnawi technically all the other tests are testing ignoreOrder: false, but i've added an explicit test.
I've also updated the package-lock file, it started failing due to npm audit.

[alexander-akait]

We need check stats.warning is empty or not in tests otherwise tests doesn't make sense

[mjhenkes]

@evilebottnawi added

[alexander-akait]

Good job, three notes

[alexander-akait]

toBe(true)

[JimLynchCodes]

just wondering why toBeTruthy(); is "better". Seems like the exact same shit to me...

[JimLynchCodes]

@evilebottnawi

[alexander-akait]

toBe(false)

[alexander-akait]

rename file ignoreOrder-option.test.js

[alexander-akait]

👍

[mjhenkes]

Do we need more approvals?

[mjhenkes]

Thanks @evilebottnawi! 🎉

[kubijo]

Yeah, thanks a lot guys!
What is the release process now?

[alexander-akait]

Today