[PERF] Issues missed by auto-filer

[DrewScoggins]

These issues were missed by the auto-filer during the 9.0 development cycle. Tracking them here, as well as tagging those who seem the most likely to be able to investigate the issue based on the changes in the commit range.

Top level issue	Date	Notes	x64 CoreCLR Win	x64 CoreCLR Lin	x64 MonoJit Lin	Arm64 CoreCLR Lin
#97202 (PR)	26-Jan	Was not auto-filed	N/A
f36aa7e...ee501fb
15-Mar	No autofile	N/A
#100160 (PR)	26-Mar	Missed by auto-filer	N/A
6931b3b...815650e	5-Aug	No autofile		N/A
16cb414...9a3cacd	26-Jan	No autofile		N/A
#97488 (PR)	29-Jan	No regressions linked but seems to be likely cause of at least 1 Linux Coreclr x64 regression		#97488 (PR)
c7d36b4...d5026a1	28-Aug	No autofile, unclear cause		N/A
#102261 (PR)	30-May	No linked regressions, may be cause of at least one on x64LinCore		#102261 (PR)
6927fea...d7ae8c6	13-Jun	No autofile, one test x64LinCore		N/A
#99541 (PR)	12-Mar	No regressions linked, but seemingly 1 x64LinCore regression missed		#99541 (Missed, Likely PR)
#106578 (PR)	18-Aug	No linked regressions and recent so unclear if potential cause		#106578 (PR)
#98610 (PR)	19-Feb	PR never linked to any regressions, though seems most likely to be cause of an Arm64 Lin CoreCLR regression				#98610 (Missed, PR)
e1c6717...0fb0188	7-May					N/A (1 Issue, Brotli.Compress_WithoutState: 7.85% reg)
9bb2b5b...60be20c	29-Nov					N/A (1 Issue, Perf_Console.ResetConsole: 6.12%)
c422fca...8c02b08	9-Nov					N/A (1 Issue, LinqBenchmarks.Order00ManualX: 5.73%)
954ead3...fae6720	13-Feb					N/A (1 Issue, Perf_Uri.EscapeDataString: 14.2%)
74f7f91...1bf325c	19-Jun					N/A (2 Issues, IPAdressPerformanceTests: Noisy NS)
#100899 (PR)	11-Apr	No regressions linked but likely cause of Arm64 lin Core ref handle stabalization to high bi-modal behavior				#100899 (PR)
ddf9fee...0d641e5	26-Jan					N/A (1 Issue, CtorFromCollectionNonGeneric: 47.94%+)
d752f9a...b29efed	26-Feb	No issue - Likely chrome bump (3 cases)

[jeffschwMSFT]

@DrewScoggins what are your thoughts on how to identify who should investigate the 20'ish issues above?

[DrewScoggins]

Sorry for the delay here. I was going to update the table here to make this a bit more actionable. I will go through and update the table with a link to the regressed test, as well as a best guess of the commit in the range that could be responsible. I will also tag the PR author.