fix: handle two busboy error events

[mhassan1]

This PR enables multer to handle two out-of-band error events from busboy; it does this by replacing process.nextTick (which happens too soon after the first error event) with setImmediate.

I don't know if this fix will handle more than two, but I also don't think busboy will ever emit more than two.

This is a follow-up to #1177.

Resolves #1176.

[mhassan1]

@UlisesGascon @LinusU Please take a look, when you have a chance. Thanks.

[LinusU]

Could you duplicate the test into a new one, instead of modifying the current one, so that we are sure that the previous single error is also handled? 🙏

[mhassan1]

Could you duplicate the test into a new one, instead of modifying the current one, so that we are sure that the previous single error is also handled? 🙏

@LinusU Done, please take a look.

[mhassan1]

@UlisesGascon @LinusU Please take a look, when you have a chance. Thanks.

[UlisesGascon]

Not sure why the CI pipeline was not triggered 🤔

[bjohansebas]

@UlisesGascon see #1302

[mhassan1]

@UlisesGascon @LinusU Are the CI failures blockers to this PR? The tests are passing on supported Node.js versions.

[ctcpip]

this looks good, but we are pulling in this fix as part of another PR. I will update when that gets merged. thank you!

[ctcpip]

waiting to merge, please hold

[ctcpip]

resolved via 2c8505f

thanks everyone!