Merge pull request #1335 from Unity-Technologies/unity-master-method-to-skip-assembly-version-validation

Add option to ignore versions when loading strong named assemblies

Fixing an issue with ManagedWebSocket 

Reintroduce https://github.com/Unity-Technologies/mono/commit/6c41f64f25da4c12b237b6bb51765722e0dd5281#diff-0ff844e784e15d2542b71c85d2c0133e

This is so we will not get errors when resolving strong named assemblies for a version not loaded.
This option will ignore the version

https://forum.unity.com/threads/current-netstandard-2-0-system-net-websocket-clientwebsocket-has-a-critical-bug.785366/

Fix handling invalid Windows proxy config

source: https://github.com/mono/mono/pull/12595

Re-adding whitespace to reduce diff noise and make future cherrypicks easier.

[debugger] Access invalid memory address using PointerValue Command. …

* Validate the address that came from IDE using PointerValue. The IDE can send an invalid address and it was crashing mono.

Fixes #18191
Fixes #15612
Co-authored-by: NAleksey Kliger (λgeek) <akliger@gmail.com>

Wrap create_file_to_check_memory_address in #ifndef _MSC_VER check as it's only used in that scope.

Fix random crash on OSX when pushing thread stacks

Fixing hang that would occur when a Debugger.Break would be triggered…

Fixing hang that would occur when a Debugger.Break would be triggered while we are already processing a breakpoint. (case 1254123)

Adding test for debugger hang fix to case 1254123

Added a new property to Tests class which breaks this test.

[corlib] Use Environment.Platform to access the platform, rather than…

[corlib] Use Environment.Platform to access the platform, rather than probing the file system (#6535)

Alternatve patch to: #6533

Update pip install index-url

Unity master update pe verifier

Fixing crash that would occur when a dll's import table was not filled out which is structurally valid

Repackage stevedore artifact to remove builds in folder structure

* Remove extra string copies.

* Teach metadata-verify.c about PE32+.

It is currently hard coded to this: Intel 386 or later processors and compatible processors but we can occasionally get other machine types so this winds up flagging dlls as invalid when it should not.

The fix for 1256569 broke a test. Partial revert

The fix for 1256569 broke a test. Reverting most of that change and breaking the CreateLocal -> WinRTFallback -> CreateLocal loop by calling GetLocalTimeZoneInfoWinRTFallback instead of accessing Local from within FindSystemTimeZoneByIdWinRTFallback fixes both issues.

Need to make sure we don't duplicate the timezone and create a new local when we already have one.

X509ChainImplUnityTls reports status now

Fixes Fogbugz ticket 1261388.
Impl sticks close to current Mono Btls implementation on _master_ - the implementation on our fork has the same issues as prior to this fix and throws NotImplementedException

Fix TLS offset lookup on macOS ARM64

Fix "Found new TLS offset at 224" log message when running on macOS ARM64 by adding a known TLS offset of 224 (0xE0).

Use mono_runtime_invoke to invoke finalizers.

Add a null check before invoking finalizer. Before, we would do a callvirt Finalize() on the object and if it didn't have a finalizer, it would call Object::Finalize(). However, since now we use mono_method_invoke with a concrete method, we crash if it's null. So we just

Use mono_runtime_invoke to invoke finalizers. This way managed runtime can do whatever is necessary to transition to executing managed code, like marking JIT memory executable on macOS ARM64.

Exposing functions: mono_custom_attrs_construct_by_type and mono_unit…

* mono_custom_attrs_construct_by_type allows unity to have a chance at handling the error if one arises instead of fatally asserting
* mono_unity_error_convert_to_exception allows unity to take the provided MonoError and fetch the MonoException object within to log into the editor as the exception that was thrown.

This change has associated unity changes in order to fix (case 1255935)

Pickup BDWGC fix for GC_retry_signals performance regression (case 1255866)

Retry running bee several times if it fails