feat: Limit route info events to 3 recent entries

[ttizze]

Description

Issue

During extended development sessions, route information continuously accumulates in memory as new loader/action events are processed. This leads to:

• Increasing memory consumption
• Potential performance degradation
• Unnecessary storage of old event data

Changes

• Added a limit to store only the 3 most recent events for each route's loaders and actions
• Applied slice(-3) to both loader and action event arrays

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Unit tests

Checklist:

• My code follows the guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[AlemTuzlak]

Interesting, I wonder if this could be a config option on how many you want to save instead of deciding for the user, eg you can set it to 3,5, 30

[ttizze]

I'm not sure about all the details, but how about something like this?