Edge distance triggers don't automatically account for different localcoords

[potsmugen]

Describe the bug

Unlike position and velocity and some other triggers, edge distance triggers currently don't account for different localcoords. This means the following triggers:

backedgedist
backedgebodydist
frontedgedist
frontedgebodydist
stagefrontedge
stagebackedge

Return the same values even when a character with one localcoord redirects them to another one with a different localcoord.

(There might be more such cases but it's hard to find them.)

To Reproduce

1. Put KFM againts KFM 720
2. Use this to debug KFM:

[State -2, Debug]
type = displaytoclipboard
trigger1 = 1
text = "P2BED = %d P2BEBD = %d P2FED = %d P2FEBD = %d"
params = enemy, backedgedist, enemy, backedgebodydist, enemy, frontedgedist, enemy, frontedgebodydist
ignorehitpause = 1

The return will be different between Mugen 1.1 and Ikemen GO.

Expected behavior

Same as Mugen 1.1

Screenshots / Video

Mugen 1.1

Ikemen GO (latest)

Engine Version (or source code date)

24/03/2023

Operating system

Windows

Extra context or search terms

No response