Persistent filter state between reports and runs pages

[feyruzb]

This pull request refactors and improves the filter preset handling in the report filter components. The main goals are to streamline preset application (especially via URL), improve state management during initialization, and clean up related code. The most important changes are grouped below:

Preset Application and Initialization Improvements:

• Added a new function selectPresetSilently to PresetMenu.vue for setting the active preset without triggering UI side effects, supporting smoother preset initialization via URL.
• Enhanced the initialization flow in ReportFilter.vue by introducing an isInitializing flag and updating initByUrl to properly handle preset application from URL parameters, ensuring correct state and preventing race conditions.
• When clearing all filters, the filterPreset parameter is now removed from the URL, ensuring the UI and URL remain in sync.

Code Refactoring and Cleanup:

• Split the logic for building preset query parameters into a new buildPresetQuery function, and separated preset application into initFilterPreset and initFilterPresetFromUrl for clarity and reuse.
• Removed the old getFilterPreset function and updated event handling so that applying a preset now uses the improved initFilterPresetFromUrl logic.

State and Reactivity Enhancements:

• Refactored the logic for tracking filter modifications into a checkModified function for better reusability and clarity, and ensured it is called at the appropriate times.

These changes collectively make preset management more robust, maintainable, and user-friendly, especially when dealing with URL-driven state.

[gulyasgergely902]

One question otherwise LGTM

[gulyasgergely902]

If you already query the route, wouldn't it be easier to just pass it to the checkModified function instead of querying it again inside it? Please check the feasibility of it.

[gulyasgergely902]

Remove unnecessary new line.