Migrate from tsimp to swc

[mattdean-digicatapult]

Pull Request

Checklist

• Have you read Digital Catapult's Code of Conduct?
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

PR Type

Please delete options that are irrelevant.

• Bug Fix
• Chore
• Feature
• Documentation Update
• Code style update (formatting, local variables)
• Breaking Change (fix or feature that would cause existing functionality to change)

Linked tickets

https://digicatapult.atlassian.net/browse/SQNC-20

High level description

Migrate from using tsimp as our typescript runtime compiler to using swc

Detailed description

Similar to digicatapult/veritable-ui#172.

Note there's a known bug with swc-node where node_modules imports with a package ending in .js fails (see swc-project/swc-node#865). We hit this as polkadot.js uses bn.js internally. The workaround here involves implementing our own shim that bypasses swc-node in this particular case.

Note I've additionally tested brining this up in a built container and it all works

Describe alternatives you've considered

Not upgrading until swc-node fixes this. Note though that this bug has been reported for several weeks with no sign of it being fixed. Hence I'm putting this forward as an alternative so we can move away from tsimp which is just not production ready.

Operational impact

None

Additional context

N/A