[BUG]: Exceptions aren't correctly set up for ARM 64 architecture

### Describe the bug

Any code throwing an exception seems to yield a segmentation fault when run on an ARM64 architecture, both with clang and gcc.

### Steps to reproduce

1. Visit godbolt.org
2. Choose any recent ARM64 (e.g. ARM 64 gcc 15.2.0)
3. Run the following snippet:

```c++
#include

int main()
{
try
{
std::vector empty;
int foo = empty.at(1);
}
catch(...)
{

}
return 0;
}
```

### Expected behavior

Output like:

```
ASM generation compiler returned: 0
Execution build compiler returned: 0
Program returned: 0
```

(obtained x86-64 gcc 15.2.0)

Instead we get:

```
ASM generation compiler returned: 0
Execution build compiler returned: 0
Program returned: 139
Program terminated with signal: SIGSEGV
```

### Reproduction link

https://godbolt.org/z/M7fYf8xPv

### Screenshots

Not applicable

### Operating System

NA

### Browser version

Firefox 144.0.2 (aarch64)

Start with the reproduction link and run the provided C++ snippet on ARM64 gcc and clang, then compare it with the x86-64 result. Trace the compiler-explorer execution path for ARM64 exception handling; done means the exception is caught and the program returns 0 instead of terminating with SIGSEGV.

Written by the indexing model from the issue text.