BugBot is too keen to move bugs to components ("search", "bookmarks"), despite previous examples of moving them back.

STR

1. The update_bot files a bug in Fenix::General for an application services update.
2. The update happens to mention search (amongst other things).
3. botbot comes along and moves it to Fenix::Search.
4. We then move it back to Fenix::General because it isn't specific to search.
5. Wait to the next update and go back to the first step.

Actual Results

Every time there's a release, someone has to move the bug back again.

Expected Results

The bot should learn, or be able to be told never to move bugs like this.

As a side note, I've also seen that the bot appears to be overly keen to move bugs. I'm pretty sure that in a lot of instances the first comment only has to have the word "search" in it to be moved to the search component (of Fenix or Firefox), and similarly "bookmarks" to get to the Bookmarks & History component in Firefox, even though the bug might be talking about address bar or profiles.

Start by tracing the component-move logic responsible for matching terms such as “search” and “bookmarks,” then inspect any existing tests for component assignment. Reproduce the described Fenix::General case and verify that repeated updates do not move it to a more specific component without sufficient evidence or an exclusion rule.