Rider Debugger Issue – Stepping into Unity Package Cache

I am experiencing an issue when debugging a Unity project in Rider 2024.3.6.  

Issue description:  
When stepping through the code using F8 (Step Over), Rider unexpectedly jumps into Unity’s internal package cache. This causes Rider to start debugging Unity’s API code (e.g., `Button.cs` from UnityEngine.UI) instead of returning control to my script. The more I press F8, the deeper it goes into Unity’s package source files, making debugging extremely difficult.  

Reproduction steps:  
1. Open a Unity project in Rider (I am using Unity 6000.0.34f1).  
2. Attach Rider’s debugger to Unity.  
3. Set a breakpoint inside a method that is invoked by a UI Button.  
4. Start debugging and use F8 (Step Over).  
5. Instead of returning control to my script, Rider enters Unity’s package cache code.  

What I have tried:  
- Ensured that Enable external source debug is disabled in Rider.  
- Verified that Unity is set to use Rider as the external script editor.  
- Checked Step Filters (but they seem to apply only to JavaScript).  
- Attempted various Unity Player Settings, including Managed Stripping Level adjustments.  
- Restarted Rider and Unity multiple times.  

Despite these attempts, the issue persists. Is there a way to prevent Rider from stepping into Unity’s internal code while debugging?  

I would appreciate any guidance or workarounds to resolve this issue.