Fix RotationCount being invalidated when Mystery Raids are inserted

When a Mystery Raid was created and inserted into the ActiveRaids list,
it would shift all raids at or after the insertion position. If RotationCount
pointed to a raid at or after this position, it would end up pointing to the
wrong raid (typically the newly inserted Mystery Raid instead of the intended
configured raid).

Changes:
- Adjust RotationCount after inserting a Mystery Raid if insertion happens at or before current position
- Add logging to track when RotationCount is adjusted

This ensures the "Next Raid Up" embed matches what actually gets played.

Author: hexbyt3

SysBot.Pokemon/SV/BotRaid/RotatingRaidBotSV.cs

@@ -1719,6 +1719,13 @@ private void CreateMysteryRaid()
             // Insert the new raid at the determined position
             _settings.ActiveRaids.Insert(insertPosition, newRandomShinyRaid);
 
+            // Adjust RotationCount if the insertion shifted the current raid
+            if (insertPosition <= RotationCount)
+            {
+                RotationCount++;
+                Log($"Adjusted RotationCount to {RotationCount} after Mystery Raid insertion at position {insertPosition}.");
+            }
+
             Log($"Added Mystery Raid - Species: {(Species)pk.Species}, Seed: {seedValue}.");
         }