* Setup internal feeds in internal builds

* Add 8 explicitly for now

* Fix condition on mono-wasm workloads

This reverts commit 0bfc0c9e.

* [RISC-V] Initial commit for libraries directory

* Update src/libraries/System.Reflection.Metadata/tests/PortableExecutable/PEHeadersTests.cs
Co-authored-by: NJan Kotas <jkotas@microsoft.com>

---------
Co-authored-by: NJan Kotas <jkotas@microsoft.com>

Microsoft.Dotnet.Sdk.Internal
 From Version 9.0.100-alpha.1.23461.3 -> To Version 9.0.100-alpha.1.23462.26
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Change "in" modifier to "ref readonly" to avoid warnings
in existing interop code.

Update dependencies from https://dev.azure.com/dnceng/internal/_git/dotnet-optimization build 20230912.6 (#91998)

optimization.linux-arm64.MIBC.Runtime , optimization.linux-x64.MIBC.Runtime , optimization.windows_nt-arm64.MIBC.Runtime , optimization.windows_nt-x64.MIBC.Runtime , optimization.windows_nt-x86.MIBC.Runtime , optimization.PGO.CoreCLR
 From Version 1.0.0-prerelease.23458.2 -> To Version 1.0.0-prerelease.23462.6
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Microsoft.CodeAnalysis.Analyzers , Microsoft.CodeAnalysis.NetAnalyzers
 From Version 3.11.0-beta1.23458.1 -> To Version 3.11.0-beta1.23462.3
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

We currently are unable to get SPMI diffs for methods that use ldapur
instructions as our current coredistools does not support this
instruction. While we wait for coredistools to be updated (this was
blocked on some C++ lib issues) here is a hacky temporary workaround for
the problem. It rewrites ldapur* instructions into the corresponding
ldur* instruction before passing it to the near differ.

* Optimizing initializing SIMD vectors with some zero elements.

* Fix x64 case.

* Fixed zero checking for floats.

Align attribute name and semantics with the OpenTelemetry spec .

* Added asserts to send buffer helper

* Postpone confirming the last RECEIVE event until the data are read

* Removed lock

* Debug tests

* ReadsClosed test fixed, and some better logging

* Final task keep alive, abort order, timeout for graceful write-side shutdown in dispose, named constants

* Tests

* Always wait for SEND_COMPLETE

* Exclude BigPayload on platforms where it can OOM

* Removed unintended code changes

* Reverted postponing reading FIN, if data have chance to get buffered with FIN, we will do that.

* Clean ups

* Fixed waiting for SEND_COMPLETE

* Hold back setting FinalTaskSource and overwrite result if no waiter is there

* Cancellation and completion

* Comments, fixed FinalTaskSource

* Fix assert

* Test reseting control stream made more resilient

* Attempt to fix still running write while disposing the stream in case of a cancellation

* Attempt to fix stress build

* Sync Dispose in H3Stream waits for read and write as well

* Non-smoke MT tests.

* Disable tests: System.Timer, Threading, Local

* System.Threading.Tasks is mostly fleaky, cannot block one by one.

* Threading.Task.Parallel - ParallelForeachPartitioner and ParallelForTests are fleaky, cannot define which tests fail, blocking suspicious ones.

* No tests can be run in MT.

* Fails even when no tests enabled.

* System.Runtime disable failing tests.

* To be reverted! Apply tmp dev speedup suggested.

* System.Runtime.Serialization.Xml.Tests disabled.

* System.Runtime.Extensions.Tests disabled.

* System.Private.Xml.Tests disabled.

* System.Linq.Parallel.Tests disabled.

* ystem.IO.Pipelines.Tests disabled

* System.Globalization.Tests disabled.

* System.Composition.Tests disabled.

* System.ComponentModel.TypeConverter.Tests disabled.

* System.Collections.NonGeneric.Tests disabled.

* System.Collections.Concurrent.Tests cannot define which tests are failing, disable full project.

* Microsoft.Extensions.Logging.Console.Tests disabled.

* Microsoft.Extensions.Http.Tests disabled.

* Microsoft.Extensions.HostFactoryResolver.Tests disabled.

* Microsoft.Extensions.Configuration.Functional.Tests disabled.

* Microsoft.Extensions.Configuration.EnvironmentVariables.Tests disabled.

* Disable samples on mt.

* For non-mt it should stay excluded.

* Revert ab5472c6a1dcaae5289ddee2f5b200b64482eb47

* Fix a copy-paste error.

* Default: only smoke.

* Duplicated job suffix, after disabling failing tests we should fail on error.

* Feedback - revert shouldContinueOnError removal.

Fixes #85146.

* Add documentation about contributing to config binder generator

* Address feedback and make misc improvements

Microsoft.Dotnet.Sdk.Internal
 From Version 9.0.100-alpha.1.23453.2 -> To Version 9.0.100-alpha.1.23461.3
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

This fixes out-of-bounds access when trying to write the
diagnostics info on platforms where the PAGE_SIZE is larger
than the DumpWriter's 16KiB m_tempBuffer.

Make Options source gen support Validation attributes having constructor with params Parameter (#91915)

Disabling HTTP/3 test `LargeSingleHeader_ThrowsException` against #74896 because it's happening quite often until we're back to investigate it.

Related to #91757

* Mark SString's single ctor's as explicit

Add move ctor to SString and SBuffer
Address all places that were implicitly allocating

After #89654 SPMI replay will succeed instead of result in replay errors
in expected error cases (such as BADCODE or EE exception). To support
diffing such contexts, we record zero-sized assembly that the near
differ uses. However, on arm64 there is some additional code that calls
repCompileMethod to make some additional adjustments to the code blob,
and in the "EE exception" cases we cannot replay this function,
resulting in crash during asmdiff. This fixes the problem by only making
the adjustments when we know there is any code.

An alternative solution could be to avoid invoking the neardiffer at all
in the succeeding error cases, but this seemed like an ok pragmatic
solution.

Fix #91257

Since CMD does not strip quotes from arguments passed in with quotes
by default, if a Nuget package cache path containing a space is
passed to build-runtime.cmd, it will pass it into an additional CMake
argument with an additional set of quotes.

This causes string semantics to be disabled upon reaching the
second opening quote, thus separating the cache path into two
separate arguments incorrectly, resulting in the PGO data optimization
pointing to an invalid path.

This patch fixes this issue by simply removing the redundant quotes
when accepting the arguments in build-runtime.cmd.

This is a leftover from .NET Native.

I had things configured wrong for the hackathon, but this seems like an improvement. We gate ValueType Equals on the same thing.