feat: RA_Integration support, Input Combos, UI/OSD overhaul & stabili…

[CySlaytor]

…ty fixes

• Added support for RA_Integration (Windows) to load the official RA DLL and developer toolset.
• Implemented Achievement audio feedback with rarity logic (Unlock vs Rare Unlock).
• Added cross-platform audio playback (SDL2 for Desktop; SoundPool for Android).

Input System:

• Reworked savestate hotkey binding logic.
• Reorganized mapping UI; moved Emulator section into Emulator Hotkeys.
• Merged duplicate bindings (Fast Forward, Menu, etc.) to eliminate redundancy.
• Correctly distinguished Fast Forward (Toggle) vs Fast Forward (Hold).

Hardcore Mode:

• Prevented loading savestates while allowing savestate creation for debugging and ticket purposes.
• Maintained restrictions on pause, frame advance to prevent abuse.

UI/OSD Overhaul:

• Reworked overlay layout system to prevent collisions between indicators.
• Moved Trigger indicator to bottom-right to avoid overlap with Measured indicator.
• Implemented symmetrical slide-in/out animations for Trigger notifications.
• Converted achievement unlock dismissal to slide-out for animation consistency.
• Fixed multiple race conditions between Trigger/Measured indicators and unlock notifications.
• Decoupled overlay lifecycles to prevent premature dismissal of achievement cards.

Leaderboard Improvements:

• Fixed conflict where active leaderboard counters blocked Measured indicators.
• Implemented dynamic stacking and automatic slide-up/down repositioning.
• Supported multiple simultaneous leaderboard counters.
• Reworked leaderboard submission/cancel cards:
  • moved to top-left alignment;
  • replaced slide animation with fade in/out;
  • enabled stacking of multiple submissions occurring on the same frame.

[flyinghead]

Can you target the dev branch instead? Thank you

[CySlaytor]

Thanks! I've updated the target to dev. I'm going to draft what I've done so far here.

[flyinghead]

I just merged master into dev since it was needed anyway. You should just have to merge into your branch to get rid of these unwanted commits.

[CySlaytor]

I've performed a hard reset. The PR should now only show my single commit against the dev branch. Let me know if I should close this PR and retarget again or resume from here. I apologize for the inconvenience. Thanks!

[flyinghead]

No need to recreate a PR at this point.
The next issue is the amount of white space changes, which makes it hard to detect the actual changes. Some files only have white space changes (core/ui/gui.h at least).
I would appreciate if you could limit changes to the code sections that need it.

[CySlaytor]

Bummer; that's a really nasty diff to look at. I honestly have no idea how that happened. When I make changes to the codebase, I usually refork and rebuild CMake and recompile repeatedly, since I plan to squash everything into one clean commit. But yeah; the diff looks absolutely terrible right now.

[CySlaytor]

@flyinghead I'm going to close this PR in order to fix those white spaces. I also wanted to submit a detailed form that explains the changes I've done so far. Thanks!

[vkedwardli]

Besides the random indentations changes, to be honest this PR is a bit too large and covering different areas.
Better group relevant features together, and split into different feature branch using dev as your base branch

[flyinghead]

Feel free to create a new PR if it helps.
I do agree with vkedwardli that more than one PR, each focused on a particular area or change, would be easier to manage and accept.