fix: type should match cjs format

[albertodeago]

Types are not correct, they are not aligned with the code.
Similar to onebeyond/systemic#69

Related Issue

Didn't open an issue, should I do it?

Motivation and Context

This is an issue users encounter if they try to consume this module from an ESM service.

export default runner should be used if in the js file we were doing export default runner; -> the package is exported as a ES module.
When exporting a CJS module instead (like we're doing here with module.exports = ...) the type definition should be export = runner;

Typescript is probably clever enough to not raise any error when consuming this in a CJS service, but in an ESM environment it's raising an error, see screenshot

How Has This Been Tested?

This is a change only in the types, I've tried it changing the type definition directly in the node_modules both in a ESM service and in a CJS service

Working in CJS service

Working in ESM service

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[UlisesGascon]

I will include this change in the next release @albertodeago! Thanks for the fix 👍

[albertodeago]

Thank you guys for the quick work! 🚀

[UlisesGascon]

Hey @albertodeago should be ready in systemic-service-runner@3.0.0 the major is due a license change (ISC to MIT) that was pending to be released for a while... 😅

[albertodeago]

Amazing, thanks @UlisesGascon 🙏