[Bug]: Unintended back navigation occurs when rapidly tapping the back button in `topicScreen`

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Is there a StackOverflow question about this issue?

- [X] I have searched StackOverflow

### What happened?

When rapidly tapping the back button in the `topicScreen` component, unintended back navigation occurs. The current implementation of the `onBackClick` directly calls `listDetailNavigator.navigateBack()` without first checking if navigation is allowed, leading to unexpected behavior.

I expected the back navigation to occur only when it is allowed, preventing any unintended navigation when the back button is tapped multiple times in quick succession. Specifically, the `onBackClick` should check `listDetailNavigator.canNavigateBack()` before calling `navigateBack()` to ensure that the back navigation is permitted.
```kotlin
topicScreen(
showBackButton = !listDetailNavigator.isListPaneVisible(),
onBackClick = {
if(listDetailNavigator.canNavigateBack()) {
listDetailNavigator.navigateBack()
}
},
onTopicClick = ::onTopicClickShowDetailPane,
)
```

In typical scenarios using a standard `navController`, this issue can be avoided by checking the lifecycle state of the `navBackStackEntry` before popping the back stack:
```kotlin
if (navController.currentBackStackEntry?.lifecycle?.currentState == Lifecycle.State.RESUMED) {
navController.popBackStack()
}
```

### Relevant logcat output

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Start at the topicScreen entry point and inspect its onBackClick callback and the listDetailNavigator methods it uses. The change is complete when repeated back taps only navigate while canNavigateBack() allows it; no test file is named in the issue.

Written by the indexing model from the issue text.