Add new rule for detecting potential performance-related bugs

[PromiseFru]

New rule for detecting potential performance-related bugs.

Checklist

• Type annotations added to new functions
• Docs added to functions touched in main classes
• Dry-run produced the expected results
• The to-be-announced tag added if this is worth announcing

[PromiseFru]

Dry-Run

Hi there,

    <p>
The following bugs are probably performance related and don't have performance impact value:

Bug	Summary	Confidence (%)
1876285	Constant high cpu & gpu usage + framerate degredation on beatport.com	25
1876263	See how much we can optimize `all` transition handling.	24
1876157	Nightly-as-release builds are slower than regular Nightly builds (not PGO'ing properly)	35
1876051	test_fetch perf test takes a long time with http/3	28
1875469	High CPU use on gmail.com due to exzessive window.message usage (blocking other tabs from loading)	32

Sincerely,
BugBot

See the search query on Bugzilla.

    <p>
        See the source / report issues on the <a href="https://github.com/mozilla/bugbot/">GitHub repo</a>
    </p>
</body>

[suhaibmujahid]

Please fix the CI :)

[suhaibmujahid]

Thank you! LGTM. Could you please add the rule to the daily tasks (in the scripts/cron_run_daily.sh file)?