* Pass more information about execution mode to RegexRunners

Some engines, in particular NonBacktracking, are relatively pay-for-play, in that the more information you need, the more processing they do.  However, we currently don't pass enough information down to the RegexRunner to allow the engine to take full advantage.  Today NonBacktracking can short-circuit its evaluation if it's told IsMatch is being used, but with the new EnumerateMatches and Count (and some uses of Replace), it's still gathering up all of the capture information even though that capture information will be ignored.  This commit introduces a new RegexRunnerMode enum that lets us pass down to the engine exactly what portion of the information is needed, allowing it to avoid unnecessary work.

Related, we can reduce the amount of work performed by Match.Tidy: if the captures information won't be used, there's no point in fixing up the positions.

As part of this, I noticed we have a race condition in the new EnumerateMatches.  We want to extract the index, length, and new text position from the Match object in order to populate the enumerator and result structs, but today we're doing so after the runner is returned to the cache.  That means another thread could come along and start using that same Match object while we're still using it in the EnumerateMatches call.  The fix is to extract the data from the Match before returning the runner.

* Address PR feedback

* Address PR feedback

* Do not reset the assignedInterval again

* Add test case

* TestEventListener

* Feedback

Fixes #68257

Extracted from https://github.com/dotnet/runtime/pull/67771 to get the fix for https://github.com/dotnet/runtime/issues/67349

Updates the WASM tests to always use net6.0 until we can upgrade to a net7.0 SDK.
Co-authored-by: NPremek Vysoky <premek.vysoky@microsoft.com>

* add more diagnostics to LookupProperty flaky tests

* Fix nullability issue on Release build

* Update TestHandleCollector() test

Initialize local member in HandleCollector
   since it was the only one not initialized.
Update test to wait for pending finalizers since that is when
   the HandleCollector API will trigger the GC.
Co-authored-by: NElinor Fung <elfung@microsoft.com>

* Add API entry for JsonDocument converter

* Add reference to System.Text.Json

* Add JsonElementConverter from MetadataServices

* Correct converter naming

* Add JsonDocument type to source generation

* include testing
Co-authored-by: NEirik Tsarpalis <eirik.tsarpalis@gmail.com>

* Add retries to ModulesAreDisposedWhenProcessIsDisposed

* Update src/libraries/System.Diagnostics.Process/tests/ProcessModuleTests.cs
Co-authored-by: NAdam Sitnik <adam.sitnik@gmail.com>
Co-authored-by: NAdam Sitnik <adam.sitnik@gmail.com>

The recent change around timeouts appears to have made the timeout used in this test more accurate, which makes it more likely to fire, which is tripping up CI on slower machines.  There's no need for a timeout in this test, though; just delete it.

* Use generic math in Enumerable.Sum/Average

* Address PR feedback

* Use generic math to dedup Enumerable.Min/Max

* Address PR feedback

* fix the srcBufferLength check

* trigger superpmi replay job when changes to superpmi tool

* Add test that fails

* fix

* Fix test failing unelevated

* annotate

* overflow

* Apply suggestions from code review
Co-authored-by: NRobin Lindner <robin@deeprobin.de>

* Apply suggestions from code review
Co-authored-by: NAdam Sitnik <adam.sitnik@gmail.com>
Co-authored-by: NRobin Lindner <robin@deeprobin.de>
Co-authored-by: NAdam Sitnik <adam.sitnik@gmail.com>

* Added Fix For System.CodeDom.Tests

* Added Fix for Microsoft.XmlSerializer.Generator tests

* Removed unnecessary File IO

* Substituted LineEndingsHelper.Normalize

The runtime is creating the exception so we need to preserve it.
See https://github.com/xamarin/xamarin-android/issues/6626

While looking at this I noticed that `FirstChanceExceptionEventArgs` is in ExceptionNotification.cs for some reason, fixed the filename to match the type name.

Use DynamicDependency for preserving `FirstChanceExceptionEventArgs` and `UnhandledExceptionEventArgs`

* Use OpenSSL 3 on macOS

* Update documentation

* Restart CI

The virtual vector instruction used internally by the JIT were leaking out and reported as unsupported

Fixes #68222

CallArgABIInfo::ArgNum is essentially unnecessary now that arguments are
stored in order so remove it.

Also address some feedback from the refactoring and fill out some
function headers.

* Exposing ExpM1, Exp2, Exp2M1, Exp10, Exp10M1, LogP1, Log2P1, and Log10P1

* Adding tests covering ExpM1, Exp2, Exp2M1, Exp10, Exp10M1, LogP1, Log2P1, and Log10P1

* Ensure Log10P1Test64 is 64-bit only

Fix #58874
Fix #64802
Fix #68157

Currently the JIT's constant folding (gtFoldExprConst and VNs
EvalOpSpecialized) assumes that BSWAP16 zero extends into the upper 16
bits. This was not the case, and in fact the behavior of BSWAP16
depended on platform.

Normally this would not be a problem since we always insert normalizing
casts when creating BSWAP16 nodes, however VN was smart enough to remove
this cast in some cases (see the test).

Change the semantics of BSWAP16 nodes to zero extend into the upper 16
bits to match constant folding, and add a small peephole to avoid
inserting this normalization in the common case where it is not
necessary.

Fixes #67723
Subsumes #67726

It allows them to be inlined by the R2R compiler.

We load the library dynamically after #55037 so it is not necessary to have the export lib available for the build.

Number of HRESULTs and error messages related to GAC, CAS and other concepts remove in .NET Core
existed just to provide mapping in Marshal.GetExceptionForHR API. They were otherwise unused.

Deleting these HRESULTs is observable behavior change in Marshal.GetExceptionForHR. It should be
acceptable change given that these HRESULTs are never returned by the runtime and very unlikely to
be used by user code.

* Avoid duplicate Strings.resx import & code-cleanup

Fixes https://github.com/dotnet/runtime/issues/68218

Makes assemblies with String.resx resources smaller by avoiding the duplicate resources.

* Overhaul when/where we check for timeouts

Regex timeouts have never been about guaranteeing exact timeout handling; rather, they're about avoiding catastrophic backtracking.  As such, we already allow an O(n) amount of work in many cases between timeout checks.  This change formalizes that, such that we now check for a timeout at every place where we could do at least an O(n) amount of work, which essentially means every time we match at a new index and every time we backtrack.  It also removes the counting logic that previously translated only 1 out of 1000 CheckTimeout calls into a timeout check; now every CheckTimeout will query the current tick count.

* Address PR feedback

* Enable System.Text.Json tests on netfx (#63803)

* Enable System.Text.Json tests on netfx

* use NETFRAMEWORK define

* disable another two test cases after rebase

* disable last test case which repros only on CI for me

* add p2p only on netfx

* Remove hardcoded assembly qualified names

* Address feedback
Co-authored-by: NKrzysztof Wicher <kwicher@microsoft.com>

Remove one of the quirks added in the call args refactoring.

* Remove all Unix-specific files.

* Throw PNSE on non-Windows.

* Merge the Windows-specific files into their formerly cross-platform counterparts.

* Remove all mentions of Unix in the tests.

* Remove two always-on defines.

* Merge two item groups in the project file.
No reason to sort them; the list is already unsorted.
And rename a remaining formerly Windows-specific file.

* Remove the NoCOMWrappers files.

* Fail on unsupported platforms when a library is trying to be loaded.

* Fix compile errors.

* Small changes in the project file.

* Remove two meaningless asserts.

* Run BinaryFormatter tests on SDC types only on Windows.

* Use `[ThreadStatic]` in Gdip.ThreadData.

* Remove `TargetsAnyOS`.
Co-authored-by: NViktor Hofer <viktor.hofer@microsoft.com>

* SDC project file clean-up

* Remove `!!` from System.Drawing.Common.
Co-authored-by: NViktor Hofer <viktor.hofer@microsoft.com>

* Exclude all markdown files from triggering CI

Since 08/09/2021 it's now possible to use wild cards in exclusion patterns: https://docs.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-192-update#support-for-wild-cards-in-path-filters.

Fixing our exclude yml statements to ignore all markdown files in the repo and not just the ones under docs/.

See https://github.com/dotnet/runtime/pull/68221