deprecate delf and dwasm

[terminaldweller]

delf and dwasm are both experimental features. they were written in python since it would be faster to try them out and more importantly I wanted a python pipe inside bruiser for later use(doesn't hurt that we were actually testing/using it).
faultreiber and luatablegen will provide the same functionality as those two. It will be faster and more manageable since they're both code generators.
I need to test luatablegen some more and then test their integration together, initially for WASM then we can do the same for ELF or any other file format since this way it only takes one XML file to get all those functionalities into bruiser.

[terminaldweller]

After the deprecation the python pipe will remain inside bruiser. I have future plans for that.

[terminaldweller]

for the wasm side of things, luatablegen is fine now,i.e. i finally decided to let Lua handle the memory allocation and deallocation for the objects. I just register the user data's with LUA_REGISTRYINDEX and get them from there. That leaves us with faultreiber. I've added the option to use lua_newuserdata to reserve memory but currently the generated parser breaks. I'm assuming the reason behind that is Lua uses malloc instead of calloc for lua_newuserdata which means some invalid pointers are not gonna be null which the parser checks for. I obviously don't want to change Lua's source code. Which leaves me with having to use the calloc option on faultreiber and then bruiser registering everything with Lua once the parser returns the object which is slower and redundant. I guess I need to think about this a bit more.