Switch osu!framework iOS projects to use AOT compilation on release configurations

[frenzibyte]

• Depends on Fix AOT compilation failure on iOS veldrid#29
• Depends on Fix DllNotFoundException on iOS when using AOT compilation SDL2-CS#169

First step towards #5902. After recent investigations, turns out Mono interpreter isn't as efficient as AOT is, and is the cause of many minor overheads that are affecting draw time negatively.

Switching osu! to use AOT compilation is going to be a considerable effort so I'll change this on o!f first and begin investigating iOS performance on a higher scale before moving into osu!.

Note that we're intentionally not using the --interpreter=all flag here (which allows the app to fall back to interpretation for dynamic code rather than throw exception), as we don't want to rely on interpretation at all until we come across a case where we can't help it.

[peppy]

Note that we're intentionally not using the --interpreter=all flag here (which allows the app to fall back to interpretation for dynamic code rather than throw exception), as we don't want to rely on interpretation at all until we come across a case where we can't help it.

I believe this will mean switching signalr back to crap mode, which I'd rather avoid if we can (at least osu! side).

But I guess this is a per-project setting so that's fine?

[frenzibyte]

Yeah we can set this flag locally in osu! if we want to.