fix: type should match code - export default Systemic is not correct, switch to export = Systemic

[albertodeago]

Types are not correct, they are not aligned with the code.
Similar to onebeyond/systemic-service-runner#13

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 Systemic should be used if in the js file we were doing export default Systemic; -> 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 = Systemic;

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 of linked issue, it's the same

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

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]

Hey @PeterAronZentai / @nochtap can you help me with the permissions... seems like I can't land the PR. I wanted to do the release as I did for onebeyond/systemic-service-runner#13. Otherwise the types will be a bit messy 😅.

Thanks in advance! ❤️

[nochtap]

Hi @UlisesGascon
I approved the workflow!

[UlisesGascon]

It is now available in systemic@5.0.0 🥳