Include SRAM in savestates

[Techjar]

This fixes an issue with saving after loading a savestate in Pokemon Colosseum. Also seems like a good idea anyways, as SRAM is part of system state after all. Should we add a flag to not write the SRAM back to disk if it was loaded from a savestate?

[Techjar]

This does not fix the issue.

[LPFaint99]

@Techjar Games like Pokemon Colosseum have further checks than normal games
some comments here #6901.

on top of this change, you also need to only load savestates that are after the last normal save

if you have S1, S2, S3 and then do a normal save, and make S4, S5, S6. you can only load s4/5/6 otherwise you will have the same problem

[Techjar]

@LPFaint99 Yeah JMC47 inforned me that this game has some SRAM-related checks. I wonder what it's doing. As for the other part of the issue, I encountered that when testing other games. We don't have a good fix for it at this time, but if this at least partially fixes Pokemon Colosseum (so that it only has the same issue as every other game) then I guess we can merge it.

[lioncash]

Should probably include the game in the commit message description as one game that needs it for example sake, so it's stored in the repository history.