observe/observeNullable running even when the view is in the background

Steps to reproduce

Add a print statement to any observe that is called when not on screen. This is nonsensical as observe should only change visible behavior, so updating it when it is out of screen just wastes CPU and is less efficient. This was fixed in QN by using the BaseFragmentHelper binding?.root lifecycle in https://github.com/LagradOst/QuickNovel/commit/e1682d49631afe7b2b8d982761d279b8ba2cf555

Expected behavior

The observe should only trigger when the view/fragment is on screen.

Actual behavior

Any use of the observe function will always invoke the action, even if the fragment is out of view.

Cloudstream version and commit hash

ALL

Android version

ALL

Logcat

N/A

Other details

No response

Acknowledgements

• I am sure my issue is related to the app and NOT some extension.
• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I have updated the app to pre-release version Latest.
• I will fill out all of the requested information in this form.

Start by locating the observe and observeNullable implementations and compare their lifecycle handling with the BaseFragmentHelper binding?.root approach in the linked QuickNovel commit. Reproduce the issue with a print statement while a fragment view is off screen, then verify that callbacks stop off screen and resume when the view is visible.