Fix vtable relocation check on Ryujinx

[plyrthn]

On Ryujinx, svcQueryMemory reports heap addresses as being inside the module's address range, which causes get_memory_state() to return the wrong result for vtables that have already been relocated to the heap. Any subsequent guard call on an already-relocated vtable would then try to relocate it again. This broke custom moveset NROs on Ryujinx.

Adds a static registry of relocated vtable addresses. Guard functions check this before calling get_memory_state(), so already-relocated vtables always pass the check correctly.

Fixes: #73

[WuBoytH]

The pain of switch emulators.

Have you checked to see if this works on console as well?

[plyrthn]

Hahaha very agreed, I'm actually gonna push up another fix for the Tetromino mod too since that's hitting a different crash...

And no I haven't! Don't have a switch capable of it anymore. Would have to rely on yourself, or someone else! I can provide an artifact if that would work?

[WuBoytH]

Honestly, it should be fine. I didn't know what .retain() actually did so I thought you were just letting memory pile up for no reason.

[plyrthn]

Forgot to reply, yeah it shouldn't cause any issues, thank you! Hoping this means no more nro character issues on emu given those are taking off recently. :)