refactor(navigation): Use contains for route matching

Updated the navigation logic to use `String.contains()` instead of `String.startsWith()` for matching destination routes. This makes the route matching more flexible, especially for routes that include arguments.

Author: rainxchzed

composeApp/src/commonMain/kotlin/zed/rainxch/githubstore/app/navigation/NavigationUtils.kt

@@ -8,15 +8,15 @@ fun NavBackStackEntry?.getCurrentScreen(): GithubStoreGraph? {
     val route = destination.route ?: return null
 
     return when {
-        route.startsWith("HomeScreen") -> GithubStoreGraph.HomeScreen
-        route.startsWith("SearchScreen") -> GithubStoreGraph.SearchScreen
-        route.startsWith("AuthenticationScreen") -> GithubStoreGraph.AuthenticationScreen
-        route.startsWith("DetailsScreen") -> toRoute<GithubStoreGraph.DetailsScreen>()
-        route.startsWith("DeveloperProfileScreen") -> toRoute<GithubStoreGraph.DeveloperProfileScreen>()
-        route.startsWith("SettingsScreen") -> GithubStoreGraph.SettingsScreen
-        route.startsWith("FavouritesScreen") -> GithubStoreGraph.FavouritesScreen
-        route.startsWith("StarredReposScreen") -> GithubStoreGraph.StarredReposScreen
-        route.startsWith("AppsScreen") -> GithubStoreGraph.AppsScreen
+        route.contains("HomeScreen") -> GithubStoreGraph.HomeScreen
+        route.contains("SearchScreen") -> GithubStoreGraph.SearchScreen
+        route.contains("AuthenticationScreen") -> GithubStoreGraph.AuthenticationScreen
+        route.contains("DetailsScreen") -> toRoute<GithubStoreGraph.DetailsScreen>()
+        route.contains("DeveloperProfileScreen") -> toRoute<GithubStoreGraph.DeveloperProfileScreen>()
+        route.contains("SettingsScreen") -> GithubStoreGraph.SettingsScreen
+        route.contains("FavouritesScreen") -> GithubStoreGraph.FavouritesScreen
+        route.contains("StarredReposScreen") -> GithubStoreGraph.StarredReposScreen
+        route.contains("AppsScreen") -> GithubStoreGraph.AppsScreen
         else -> null
     }
 }