refactor(core): refactor strip module

[g4titanx]

closes #108

[EmperorOrokuSaki]

why is this necessary when we are just accepting the runtime and the deployment bytecodes in the cli?

see #90

[g4titanx]

why is this necessary when we are just accepting the runtime and the deployment bytecodes in the cli?

see #90

we are accepting the deployment bytecode. doesnt mean we cant also accept the runtime bytecode, it's been designed to be able to handle both in the latest, in fact this has been improved #105

[g4titanx]

this pr would be rebased after the review on #105 is done and then we can continue breaking the module down into smaller modules for more clarity and manageability

[EmperorOrokuSaki]

why is this necessary when we are just accepting the runtime and the deployment bytecodes in the cli?
see #90

we are accepting the deployment bytecode. doesnt mean we cant also accept the runtime bytecode, it's been designed to be able to handle both in the latest, in fact this has been improved #105

We only need to detect the runtime like this, when we don't have it given to us in the cli. since we are using azoth for mirage and have other high priority tasks to attend to, and we are always supplying the runtime, we should deprioritize this.

i'm going to park this for now. let's clean up #90 and have it merged

[g4titanx]

okay then i'd add to my task for the day