Feature/route based navigation

[KVV94]

Ticket № 2645

closes #2645

Problem:

Currently, the selected node state is managed through application state, making navigation less predictable and hindering the use of standard browser features (like the Back button). We need to make the node selection mechanism route-based.

Solution:

Implemented a route-based node selection mechanism through a new useSelectedNodeFromUrl hook that synchronizes URL state with the selected node state. This makes node selection more predictable and allows for better browser integration

Changes:

Added new route for selected node: mainroute/episode/{episode_id}/node/{ref_id}
Created useSelectedNodeFromUrl hook for URL state synchronization
Created useNodeNavigation hook to handle node navigation
Integrated the new mechanism into Graph/index.tsx and other components where node selection occurs
Updated existing node selection calls to use the new route-based approach
Testing:

useNodeNavigation tests:

Tests URL formation correctness
Tests node navigation functionality
Tests selected node clearing
useSelectedNodeFromUrl tests:

Tests node setting from URL
Tests node clearing when URL has no ID
Tests invalid ID handling
Notes:

Using replace: true in navigation to prevent unnecessary browser history entries
No state changes occur when node ID from URL is not found
Maintained backward compatibility with existing node selection mechanism
Browser navigation (back/forward) now works seamlessly with node selection