Bug 1816186 - Use detect-only just when we can show the re-engagement dialog

[Amejia481]

The platform team brought some concerns of the performance cost of having the detect only mode active while the user can't see re-engagement dialog. They suggested we should keep it active only when the user could see the re-engagement dialog otherwise should be disabled.

This PR disables the feature when the users can't see the re-engagement dialog until waiting time for next time that the dialog could be seem again.

Pull Request checklist

• [ ] Tests: This PR includes thorough tests or an explanation of why it does not
• [ ] Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
• [ ] Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features. In addition, it includes a screenshot of a successful accessibility scan to ensure no new defects are added to the product.

QA

• [x] QA Needed

To download an APK when reviewing a PR (after all CI tasks finished running):

1. Click on Checks at the top of the PR page.
2. Click on the firefoxci-taskcluster group on the left to expand all tasks.
3. Click on the build-debug task.
4. Click on View task in Taskcluster in the new DETAILS section.
5. The APK links should be on the right side of the screen, named for each CPU architecture.

GitHub Automation

Used by GitHub Actions.