[release/7.0] Update dependencies from dotnet/efcore

[release/7.0] Update dependencies from dotnet/runtime dotnet/efcore

[release/7.0] Update dependencies from dotnet/runtime

* Don't pack Microsoft.Aspnetcore.Ratelimiting

* Update SharedFramework.Local.props

[release/7.0] Update dependencies from dotnet/efcore

[release/7.0] Update dependencies from dotnet/runtime dotnet/efcore

[release/7.0] Merge from internal rc2 branch

* Runtime helpers update
* Test updates
* Fix build break

* Generate VS.Redist package for ANCM

* Fixup

* Add package for IISExpress

* Rename nuspecs

* Fix target order

Co-authored-by: Will Godbe <wigodbe@microsoft.com>

[release/7.0] Update dependencies from dotnet/efcore

[release/7.0] Update dependencies from dotnet/efcore dotnet/source-build-externals

[release/7.0] Update dependencies from dotnet/runtime dotnet/efcore

Co-authored-by: Mackinnon Buck <mackinnon.buck@gmail.com>

[release/7.0] Update dependencies from dotnet/efcore

[release/7.0] Update dependencies from dotnet/runtime

- incomplete w/o updates in spa-templates and a submodule update here

[release/7.0] Update dependencies from dotnet/efcore

Backport of #43515 to release/7.0

/cc @MackinnonBuck @javiercn

# Fix linking issues

Fixes an issue reported by manual testing where Blazor WebAssembly projects created from the Individual Auth template throw an exception on page load after publishing.

## Description

The problem was already fixed in `main` by making `RemoteAuthenticationService` more linker friendly. From @javiercn's comment on the original issue:

> What was happening was that the linker was erasing the parameter names of the record we were using for serializing the data

Fixes https://github.com/aspnet/AspNetCore-ManualTests/issues/1556

## Customer Impact

Customers are likely to encounter this issue, especially since one of our project templates reproduces the bug. It's expected that our project templates should be ready to publish out of the box.

## Regression?

- [X] Yes
- [ ] No

Regressed from .NET 6.

## Risk

- [ ] High
- [ ] Medium
- [X] Low

The change only involves minor restructuring to enable linker-friendliness. There are no changes to any core functionality.

## Verification

- [X] Manual (required)
- [ ] Automated

## Packaging changes reviewed?

- [ ] Yes
- [ ] No
- [X] N/A

# Add <title> to empty wasm template index.html

Add <title> to empty wasm template index.html

## Description

The new Blazor WebAssembly "empty" project template lacks a `<title>`, but (1) everyone wants a title, and (2) the `<title>` element is required by the HTML spec - we can't omit it without the document being invalid. This PR adds it.

Fixes #44335

## Customer Impact

Without fixing this, newly-created projects don't conform to the HTML spec by default. And it's just strange.

## Regression?

- [ ] Yes
- [x] No - the empty wasm template is new in 7.0

[If yes, specify the version the behavior has regressed from]

## Risk

- [ ] High
- [ ] Medium
- [x] Low

It's just adding a `<title>` element to a plain-text HTML file, equivalently to how it already appears in the non-empty template.

## Verification

- [x] Manual (required)
- [ ] Automated

## Packaging changes reviewed?

- [ ] Yes
- [ ] No
- [x] N/A

Bumps [src/submodules/googletest](https://github.com/google/googletest) from `9080381` to `93f08be`.
- [Release notes](https://github.com/google/googletest/releases)
- [Commits](https://github.com/google/googletest/compare/9080381758fad853aa17ba1c3255ee8a35e452ca...93f08be653c36ddc6943e9513fc14c7292b4d007

)

---
updated-dependencies:
- dependency-name: src/submodules/googletest
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

[release/7.0] Update dependencies from dotnet/efcore

[release/7.0] Update dependencies from dotnet/runtime

[release/7.0] Update dependencies from dotnet/efcore

[release/7.0] Update dependencies from dotnet/runtime

Signing happens at the end of the build now, even with in-build signing. The staging pipeline pushes the nupkgs. This step is not necessary, and pushes unsigned nupkgs.

* [release/7.0] Move to an RTM SDK
* Update global.json
* Update global.json
* Grab part of #43802
  - `cherry-pick`ed from d184b978

Co-authored-by: William Godbe <wigodbe@microsoft.com>
Co-authored-by: Brennan <brecon@microsoft.com>

* Upgrade Microsoft.OpenApi dependency to 1.4.3
* Update tests to use copy constructors

Using the roslyn versions provided by @jaredpar: https://github.com/dotnet/aspnetcore/pull/44072#discussion_r978887076

For: https://github.com/dotnet/aspnetcore/issues/39387

References:
- https://github.com/dotnet/aspnetcore/pull/28125
- https://github.com/dotnet/aspnetcore/pull/37764
- https://github.com/dotnet/aspnetcore/pull/44072

[release/7.0] Update dependencies from dotnet/runtime dotnet/efcore

* Get template error codes from the right processes
* Make Project actions self-checking

Co-authored-by: Chris R <Tratcher@outlook.com>

- looks like general flakiness of a couple of test classes

Co-authored-by: Doug Bunting <6431421+dougbu@users.noreply.github.com>

[release/7.0] Update dependencies from dotnet/efcore dotnet/runtime

* Update ANCM.wxs

Update DotNetCore.wxs

Update SharedFramework.wxs

Update SharedFramework.wxs

Update DotNetCore.wxs

Update ANCM.wxs

Fix x86 and x64 conditions

* Fix DotNetRedistLts_x64

[release/7.0] Update dependencies from dotnet/runtime dotnet/efcore

[release/7.0] Update dependencies from dotnet/efcore

[release/7.0] Update dependencies from dotnet/runtime