Revert "[NFC] Add error propagation to ASM emitter boundary methods"

[sjain-stanford]

Reverts #262

(context)

This breaks the assumption that the asm emitter methods never error (if they do that's a failure on the graph validation logic and needs an update). I'd like to better understand the situation that spawned this and see if there's another way to address the underlying issue (why not use debug builds for dev work)? Can you share the repro / error message and what change triggered it?

Usually if these asserts are hit (shouldn't in release builds as that code is unreachable) it is highly likely that something is off in a fresh development branch, which ideally uses debug builds. This change is also very non-uniform - doesn't hold to rest of asm emitters, so I push to revert and then revisit if there's a hidden need I'm not seeing rn.