This is required on OpenSSL 1.0.x, which is still in use on RHEL7 and CentOS7

- Change base url used for generated code
- Emit message about initial memory size, on native builds
- Don't trigger all the mono jobs based on changes in `src/mono/wasm/debugger`
- Also, truncate all protocol log messages to max line length of 64k. This reduces the proxy log file for tests from `1.0G` to `160M`.
  - truncating can be disabled by setting the environment variable `WASM_DONT_TRUNCATE_LOG_MESSAGES=1`.

Fixes #71727
Fixes #62736

Co-authored-by: NJakob Botsch Nielsen <jakob.botsch.nielsen@gmail.com>

* Update dotnet/msquic ref to release/7.0

* Regenerate using darc

* Add Directory.CreateTempSubdirectory

CreateTempSubdirectory will create a new uniquely named directory under the temp directory. This allows applications to write temporary files in a co-located directory.

Contributes to #72881

It was failing with

```
pal_ifaddrs.c(315,67): error GBA20CE26: format specifies type 'unsigned long' but the argument has type 'unsigned int' [-Werror,-Wformat]
```

- Use object instead of callback.
- Replace bind_static_method with getAssemblyExports.
- Drop MethodImplAttribute where JSExport is present.
- Drop es6 from sample folder names.

Only two `ref struct` handlers are in dotnet/runtime:
* DefaultInterpolatedStringHandler
* MemoryExtensions.TryWriteInterpolatedStringHandler

each of them only have two overloads of AppendFormatted that took
a `ref struct` (always ReadOnlySpan<char>).

DefaultInterpolatedStringHandler does have a Span parameter in a ctor,
but that one does escape to the instance, so `scoped` isn't correct there.

* Update MsQuic and use ConnectionCloseStatus in StreamShutdown

* Require MsQuic 2.1.*

* Add a few comments

We had a problem where types that put the same object instance in two different fields would see two different object instances at runtime due to two frozen objects being created for what should have been just one instance. (See the test.)

Frozen objects were deriving their identity from the field to which they were assigned to so the problem fell out from this awkward design.

The fix is actually a simplification - stop deriving object identity from field and use a "Allocation site ID" instead. The Allocation Site ID is a tuple of "Type whose cctor we were interpreting" + "instruction counter at the time of allocation". That way we can uniquely identify object instances and keep referring to objects allocated in different cctors.

I've also lifted the limitation that instance delegates can only point to objects that were assigned to some fields in a different cctor because it's no longer required to limit it.

* Prevent a memory leak when requests time out and no data is being received on the serial port. Implement a custom SynchronizedQueue to ensure completed SerialStreamIORequests are eligible for GC.

* Coarse-grained locking for queues
Co-authored-by: NDan Moseley <danmose@microsoft.com>

This reverts commit b947dd6e.

* Support managed debugging when CET is enabled

* Use DataTarget ReadVirtual function to read data
Remove RS GetLiveContext/SetLiveContext implementations
Update debugger contract

* Clean up contracts and add extra validation in SetThreadContextNeeded message

* Add OUT_OF_PROCESS_SETTHREADCONTEXT ifdef

* Add todo comment to merge ICorDebugMutableDataTarget::SetThreadContext  with HandleSetThreadContextNeeded implementation

* Use JitStdOutFile for .dasm creation

* add back logging.debug

Throw if we ever take the fall thru on a conditional branch at the end
of a method.

Related to https://github.com/dotnet/runtime/issues/73474 but doesn't
fix it: this just makes the interpreter throw instead of falling off
the end of the transformed CFG

Fixes the mono "HelloWorld" sample (src/mono/samples/HelloWorld) on
desktop platforms

## 1. Fix random HotReload test failures
Some of the hot reload tests fail randomly because they call the updated methods too early.
The tests used `Thread.Sleep(3000)` to wait for the method to get updated, and the proxy
to respond to that. And that's essentially racy.

Instead, wait for the `breakpointResolved` event, or the `scriptParsed` events for the methods,
as appropriate.

Fixes https://github.com/dotnet/runtime/issues/66024
Fixes https://github.com/dotnet/runtime/issues/72946 

## 2. Fix race in adding/removing event handlers

Use ConcurrentDictionary for event listeners, and notification handlers, since they can be modified
from different threads.

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

## 3. Fix a race condition where the tests start calling methods before the app is ready

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

* WIP: fix overflow checking

* Change limit to 9 digits

* Fixed the same bug in other places

* Remove mistake include

* Move expensive tests to OuterLoop

We were not checking the result of the ExecutableAllocator::Commit call
for mapping the RW page in the case of interleaved heaps. I've seen a
failure in the CI that seems to be caused by this - when we succeeded
committing the RX page, but failed to commit the related RW page, we
have then crashed when trying to initialize the precode stubs data.

This change adds the check to fix the problem. This causes the
LoaderHeap allocation to fail as expected in such case.

* PNSE for domain sockets on iOS/tvOS
* Re-enable some tests which SHOULD now throw PNSE

* Add lowering support for conditional nodes

* Contain conditionals

* Fix formatting

* Use AND and CMP nodes

* Fix formatting

* Remove LowerNodeCC changes

Change-Id: Icdf1828905c4a3f210b06e047ef3c0ac913d71f7
CustomizedGitHooks: yes

* Remove asserts & fix variable names

* Better contain checks for conditional compares

* Simpler contained conditions codegen

* Remove Conditional Compare nodes

* Minor cleanups

* Generate AND compare chains

* Fix unsigned compares && reduce chain check recursion

* Add compare chain tests

* Review fixes

* Use GenCondition

* Change CompareChainSize to IsValidCompareChain

* Move lowering functions to lowerarmarch

* Formatting fixes

* Fix SELECT issues

* Fix test output messages.

* Better explanations for AND chains

* Compare chains should not contain tst compares

Change-Id: I8a1761e1e89f589e1daf0318e120aae5dd3d7241
CustomizedGitHooks: yes

* Don't allow tst compares in codegeneration of compare chains

* Add tests for chains with tst compares

* Don't allow tst compares in lsrabuild of compare chains

## Issue

Currently, whenever a darc flow PR is opened, we cannot trigger different jobs based on which
dependency got updated. This is needed because in some cases, like for ILLinker, Emscripten
updates we want to trigger all the wasm jobs. But that might not be needed for some of the other
dependencies.

- This causes failures to slip through to `main`, which gets discovered after the fact as other PR
failures, or rolling build failures, creating extra work for developers.

## Solution

- This PR identifies the changed dependencies, and emits one azure variable per dependency,
which can then be used in conditions in the yml .
- The changed dependency can be checked as `dependencies.evaluate_paths.outputs['DarcDependenciesChanged.System_CommandLine']`

- Included this in the `evaluate_paths` job itself, instead of creating another job

- Also, use this for wasm jobs

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

* Improved server logging to include S.N.Quic traces as well.

* MsQuicBuffers copy given memory into native instead of pinning

This reverts commit 9865cc7a.
We believe the problematic change has been reverted so the test can be re-enabled.

- move asset related logic to separate file`assets.ts`
- split logging code into separate file `logging.ts`
- add `dotnet.wasm` and `dotnet-crypto-worker.js` to mono-config.json
- moved `readSymbolMapFile()` call to `startup.ts`
- fixed bug in `setup_proxy_console()` which didn't really copy the original `log` and `error` functions of the console and caused recursion on error.
- moved `init_crypto` after `mono_wasm_load_config` in `mono_wasm_pre_init_essential_async`
- added new resource type `js-module-crypto` and `js-module-threads`
- changed the detection of blazor startup sequence to not be disabled by presence of config, but only by config.assets having some assembly in it.
Co-authored-by: NMarek Fišera <mara@neptuo.com>

* Update dependencies from https://github.com/dotnet/arcade build 20220805.2

Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22403.1 -> To Version 7.0.0-beta.22405.2

* Update dependencies from https://github.com/dotnet/arcade build 20220805.6

Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22403.1 -> To Version 7.0.0-beta.22405.6

* Update dependencies from https://github.com/dotnet/arcade build 20220808.3

Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22403.1 -> To Version 7.0.0-beta.22408.3
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Condition ExternalConsoleManipulation_RegistrationRemoved_UnregisterSucceeds on RemoteExecutor.IsSupported (#73603)

so that accessing the result address throws exception.

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

* Add handling of generic attributes to CustomAttributeDecoder

If the attribute constructor refers to the generic T in its signature, we would throw `BadImageFormatException`. This adds handling by capturing the generic context and interpreting the signature variables when needed.

* Add tests
Co-authored-by: NMichal Strehovský <MichalStrehovsky@users.noreply.github.com>

This adds prefetching to the mark phase.

The idea is that once we have established that an object is in one of the generations we want to collect, we prefetch its memory before we determine whether we have marked it already. This is because the mark bit is in the object itself, and thus requires accessing the object's memory.

As the prefetching will take some time to take effect, we park the object in a queue (see type mark_queue_t below). We then retrieve an older object from the queue, and test whether it has been marked. This should be faster, because we have issued a prefetch for this older object's memory a while back.

In quite a few places we now need to drain the queue to ensure correctness - see calls to drain_mark_queue().

[PERF] Fix "x$PERF_PREREQS_INSTALLED was unexpected at this time" Error for Microbenchmarks (#73584)

* Try double brackets.

* Only use the bash check if running on non-windows machine, added command for running on windows machines.

* Undoing changes to if statement brackets (double to single now) as the double bracket is not necessary.

* Use the correct, previously removed command.