Tracker blocking in ADB mode / status of tracker blocking

### Please check before submitting an issue

- [x] This issue is not related to the translated version of the documentation
- [x] I know technical terms used in the documentation

### Describe the problem area

Hello, unsure if this is a bug report or a documentation issue, so I'll err on the conservative side and call it a documentation issue. (I assume the developer has a better mental model of the app and understands why things are behaving the way they are.)

The documentation says that for most apps, I can't block trackers in ADB mode (see here: https://muntashirakon.github.io/AppManager/en/#subsec:faq:block-components-using-adb).

However, I noticed that App Manager still offers me to block trackers from the view showing the list of installed apps. It seems that this indeed adds the respective rules for each selected app, but that the rules are not actually applied. Is this correct?

It's a bit misleading, because the blocking operation itself shows success ("Done" or similar). The UI and/or documentation should clarify what actually happens in this case.

Finally, is there a way to see for which applications tracker blocking is currently enabled, without exporting and looking at the rules for each app?

### Current documentation if it present

https://muntashirakon.github.io/AppManager/en/#subsec:faq:block-components-using-adb

### Describe your suggestion

Clarify what happens if I block trackers in ADB mode (i.e., rules are applied, but not run unless root is enabled later).

And/or change the UI so it won't show the block option in the first place for apps where trackers can't be blocked in ADB mode.

### Additional context

_No response_