Side effect on decompilation when instructions are hooked

### Description

I'm not quite sure if it's designed or an actual bug. Here's the case:

when call instructions is hooked,

and re-decompilation is trigered (say, when decompilation options is toggled)

Hooked code is missing in decompilation result. the `printf()` disappears

### Steps to reproduce the bug

Open any binary to hook a function call instruction, decompile or re-decompile the function

### Environment

angr 9.2.33

### Additional context

_No response_