For #28266 - Merge BrowserTrayInteractor into TabsTrayInteractor

[MozillaNoah]

PR 6 of 10 for:

• Refactor Tabs Tray's interactors #25722

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

• 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

Fixes #28266

[gabrielluong]

Just curious why couldn't we pass the TabsTrayInteractor directly here?

[MozillaNoah]

I'd have to double check, but this smelled like a hack to get around a race condition or dependency issue, so that a lambda could be called after onStart, or something, to provide the interactor, rather than have the interactor as a compile time dependency

[MozillaNoah]

TabsTrayDialog is created in TabsTrayFragment.onCreateDialog, while tabsTrayInteractor inside of TabsTrayFragment is a lateinit and instantiated inside onViewCreated