DROID-3763 App | Fix | Safe dismiss request to join screen

[konstantiniiv]

---

• I understand that contributing to this repository will require me to agree with the CLA

---

Description

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 tech-docs
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[Copilot]

Pull Request Overview

This PR fixes the issue with dismissing the RequestJoinSpaceFragment in scenarios where the fragment may not be in the proper state, thereby preventing IllegalStateException crashes. Key changes include:

• Replacing direct dismiss() calls with a safeDismiss() method.
• Adding unit tests to verify the existence, accessibility, and correct implementation of safeDismiss().
• Enhancing documentation for the safeDismiss() method.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
app/src/main/java/com/anytypeio/anytype/ui/multiplayer/RequestJoinSpaceFragment.kt	Replaces dismiss() calls with safeDismiss() and adds its implementation.
app/src/test/java/com/anytypeio/anytype/ui/multiplayer/RequestJoinSpaceFragmentSafeDismissTest.kt	Introduces tests verifying safeDismiss() existence and its access modifier, along with fragment instantiation verification.

Comments suppressed due to low confidence (1)

app/src/main/java/com/anytypeio/anytype/ui/multiplayer/RequestJoinSpaceFragment.kt:350

• Consider adding tests for the safeDismiss behavior when the fragment is not in a valid state for dismissal, ensuring that the fallback logging occurs as expected.

    private fun safeDismiss() {