Merge from public release/7.0 to internal/release/7.0 and resolve conflicts if necessary

* [7.0] Bump Ubuntu 16.04 images to 18.04

* Only remove centos 8, revert the rest

* Remove Windows.10.Amd64.Core, Windows.7 and Windows.81

Block password-less PKCS12 blobs on X509 certificate loadings/imports and Prevet AIA fetching of non-cert types.

[manual] Merge release/7.0-staging into release/7.0

This reverts commit 1182123f.

* Add Ubuntu 23.10 (Mantic Minotaur) RIDs

 * library Microsoft.NETCore.Platforms
   - added RIDs to runtime.compatibility.json
   - added RIDs to runtime.json
   - added Mantic Version Id to Ubuntu runtimeGroups.props
   - incremented ServicingVersion in Microsoft.NETCore.Platforms.csproj

* Update src/libraries/Microsoft.NETCore.Platforms/src/Microsoft.NETCore.Platforms.csproj

---------
Co-authored-by: NCarlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>

Merged PR 31140: [release/7.0] Add delay load hook for singlefilehost and enable delay load of version.dll

`coreclr` delay loads `version.dll` and adds a hook such that it loads from the system directory. In single-file, we lost this behaviour since it uses static library version of `coreclr`. This adds the same mechanism to single-file.

* [7.0-staging] Reset OOB packages from 7.0.6

* Avoid resetting M.W.C.

* Add Ubuntu 22.10 kinetic kudu RIDs

* Add required OOB package authoring changes.

---------
Co-authored-by: NCarlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>

Co-authored-by: Nwfurt <tweinfurt@yahoo.com>

[release/7.0-staging] Microsoft.NETCore.Platforms: support adding rids with '-' in the base part. (#86282)

* Microsoft.NETCore.Platforms: support adding rids with '-' in the base part.

Currently when trying to add a rid like 'linux-musl-x64'
the rid is not understood to be base = 'linux-musl', arch = 'x64'.

Instead the parser considers a potential optional qualifier.
This causes the rid to be parsed as base = 'linux', arch = 'musl',
and qualifier = 'x64'.

We know the rids being added won't have a qualifier. If we take
this into account while parsing, we can parse the rid correctly.

* Update src/libraries/Microsoft.NETCore.Platforms/src/RuntimeGroupCollection.cs
Co-authored-by: NEric StJohn <ericstj@microsoft.com>

---------
Co-authored-by: NTom Deseyn <tom.deseyn@gmail.com>
Co-authored-by: NEric StJohn <ericstj@microsoft.com>

Fix DBI loading problem on Linux (#82461)

Fixup data can assist native debugging tools in providing more accurate data

(cherry picked from commit 4c814fa0)
Co-authored-by: NAndy Gocke <angocke@microsoft.com>

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.6 -> To Version 7.0.7
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.6 -> To Version 7.0.7
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

* Add test for literal field without name reference

* Fix header name buffer allocation

* Add more tests

* Unified QPackDecoderTest test files

* Fix variable name

* Fixed HPackDecoder and ported QPack tests

* Feedback

---------
Co-authored-by: NBruno Blanes <bruno.blanes@outlook.com>

Co-authored-by: Npavelsavara <pavel.savara@gmail.com>
Co-authored-by: NIlona Tomkowicz <itomkowicz@microsoft.com>

Adds a "paramName_lastIndexMarshalled" variable to generated code that tracks the index of the last element in a collection that was marshalled. Then in the cleanup stage, we only clean up to that index. This works for single dimensional arrays of non-blittable elements.

For multidimensional arrays, this will fully initialize higher order arrays to simplify the generated logic. It is possible to avoid this and can be considered in a future PR, if we observe users of multi-dimensional arrays observing performance issues.

Co-authored-by: NDaniel Ramos <danielramos@dsomar20.redmond.corp.microsoft.com>

Adding more details to our servicing documentation, particularly around the check-servicing-labels CI leg.
Co-authored-by: NJuan Hoyos <19413848+hoyosjs@users.noreply.github.com>

* Make WindowsServiceLifetime gracefully stop (#83892)

* Make WindowsServiceLifetime gracefully stop

WindowsServiceLifetime was not waiting for ServiceBase to stop the service.  As a result
we would sometimes end the process before notifying service control manager that the service
had stopped -- resulting in an error in the eventlog and sometimes a service restart.

We also were permitting multiple calls to Stop to occur - through SCM callbacks, and through
public API.  We must not call SetServiceStatus again once the service is marked as stopped.

* Alternate approach to ensuring we only ever set STATE_STOPPED once.

* Avoid calling ServiceBase.Stop on stopped service

I fixed double-calling STATE_STOPPED in ServiceBase, but this fix will
not be present on .NETFramework.  Workaround that by avoiding calling
ServiceBase.Stop when the service has already been stopped by SCM.

* Add tests for WindowsServiceLifetime

These tests leverage RemoteExecutor to avoid creating a separate service
assembly.

* Respond to feedback and add more tests.

This better integrates with the RemoteExecutor component as well,
by hooking up the service process and fetching its handle.

This gives us the correct logging and exitcode handling from
RemoteExecutor.

* Honor Cancellation in StopAsync

* Fix bindingRedirects in RemoteExecutor

* Use Async lambdas for service testing

* Fix issue on Win7 where duplicate service descriptions are disallowed

* Respond to feedback

* Fix comment and add timeout

* Fix test condition

* Enable M.E.H.WindowsServices and S.SP.ServiceController for servicing

* Make service wait on its state before stopping (#84447)

* Fix WindowsService Tests where RemoteExecutor is unsupported

* Enable MS.W.C for servicing

* Reference latest Microsoft.Extensions.Logging.Abstractions

This package has been serviced and we compile against the serviced
version of its assemblies.

None of the directly referenced projects have been serviced so our
package doesn't restore the serviced versions.

Lift up the dependency on Logging.Abstractions to ensure we reference
the serviced package.

---------
Co-authored-by: NVladimir Sadov <vsadov@microsoft.com>

Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: NPremek Vysoky <premek.vysoky@microsoft.com>

Co-authored-by: Ncarlossanlop <1175054+carlossanlop@users.noreply.github.com>

Microsoft.NETCore.Runtime.ICU.Transport
 From Version 7.0.0-rtm.23211.1 -> To Version 7.0.0-rtm.23218.4
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

[automated] Merge branch 'release/7.0' => 'release/7.0-staging'

Co-authored-by: NJuan Sebastian Hoyos Ayala <juan.s.hoyos@outlook.com>

* Ported over changes from PR: 84339 to release/7.0

* used the MAX_YP_SPIN_COUNT_UNIT variable instead of the hardcoded value

The unmanaged native library probing documentation says to try
absolute paths without variations

https://learn.microsoft.com/en-us/dotnet/core/dependency-loading/default-probing#unmanaged-native-library-probingCo-authored-by: NAleksey Kliger <alklig@microsoft.com>

Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Co-authored-by: NAndrew Au <andrewau@microsoft.com>