* Cover release/7.0 in our pipelines
* PR feedback: Remove release/5.0 mentions in our YAML

- was "Exclusively use Azure (public) feeds (#43303)"
- Correct ref to selenium-config.json
  - fix what broke `yarn install` in these directories
- Use `yarn` in aspnetcore-components-e2e pipeline
  - also correct a missing `--frozen-lockfile`

Co-authored-by: MerlinBot

* Move builds to MacOS 11
- hosted macOS-10.15 environment is deprecated

* Use an installed XCode version

- left a bit behind after manual testing

- part of #36998
- use a separate pipeline to avoid default submodule checkout
  - we will handle dotnet/spa-templates localization separately

* Specify the current agent demands and VS version
- we require VS2022 to build native code these days
- Core-Eng really likes `1es-windows-2019[-open]` 

* !fixup! Remove extra `$(WindowsTargetPlatformVersion)` settings
- set in Cpp.Common.props
- was incorrect in common.props and led to requiring two Windows SDK versions

- see discussion starting at <https://github.com/dotnet/aspnetcore/pull/41855#issuecomment-1159030492>
- short answer: wildcards do not work in artifact paths

* Fix branch names again

* Update azure-pipelines-mirror-within-azdo.yml

* Update azure-pipelines-mirror-within-azdo.yml

* Allow explicit manual runs of mirror pipeline

* Fixup

* Fixup 2

* Try different approach

* Update .azure/pipelines/azure-pipelines-mirror-within-azdo.yml

* Update .azure/pipelines/azure-pipelines-mirror-within-azdo.yml

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

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

* Add script to mirror one internal branch to another

* Fix trigger

* params

* Fixup

* Feedback

* Only run on check-ins

* Individual -> Batched

* No repo

* Fix condition

This reverts commit 46bb449f.

* Revert "Try out 1es images (#41400)"

This reverts commit 0394ac7b.

* Update default-build.yml

* Add option to enable binlogs for manual internal builds

* Fixup

- correct build.cmd location
- generally, align richnav.yml with ci.yml
  - ignore signing, internal download args, and publish args
  - perform native build w/o rich nav and don't do installers build; both fail
- disable pipeline in PR validation
  - also remove irrelevant trigger branches

nits:
- correct name of one build step in ci.yml
- don't bother setting `$(EnableRichCodeNavigation)` or `$(OnlyPackPlatformSpecificPackages)` to `true`
  - job.yml sets `$(EnableRichCodeNavigation)` variable and `msbuild` will find that in environment
  - `$(OnlyPackPlatformSpecificPackages)` is not relevant in this pipeline; not packing

* Revert "Revert "Remove downlevel runtimes from global.json (#40393)" (#40699)"

This reverts commit 74e885aa.

* Restore 3.1

* Build .rpm packages for linux arm64

* Fixup

* Remove dupe asset manifest params

* Don't build native

* Fix RPM build condition

* Get binlog

* Fix arch

* Fixup

* No binlog

* Avoid duplicate targeting-pack RPM Build
- if an RPM containing platform-neutral executables is platform-neutral, this should be enough

* Correct RPM arch name, include in targeting pack

* Revert "Avoid duplicate targeting-pack RPM Build"

This reverts commit 77f81b8d696d663249a54c56be4a1d70fe68668f

* Rename x64 RPM to "x64"

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

This reverts commit b4ccd7ba.

- was mainly used to confirm support for Components E2E tests
- those tests built more often than required

nit: do not set `$(SkipTests)` to `false`

* Use `-noBuild` in second build steps of test jobs
- building again in Publish target adds nothing in most cases
- use `-noBuildRepoTasks` more consistently
  - again, building the repo tasks wastefully repeated work done in previous build step
- use `-noBuildJava` more consistently in quarantined pipelines
  - Java tests aren't worth testing _or building_ in these pipelines because they cannot be quarantined
- remove `-noRestore` and `-noBuildDeps` when `-noBuild` specified; redundant
- work around https://github.com/dotnet/sdk/issues/23777
  - do not publish .cshtml files of most test asset projects when `$(NoBuild)` is set
- update FunctionalTestWithAssets.targets to help Publish succeed when `$(NoBuild)` is set
  - fixes build jobs in quarantined-pr pipeline where `--no-build` was already specified
- for IIS test assets, perform all builds needed for their profiles within Build target
  - move `ReferenceTestTasks=false` and comments about it to where property matters
  - merge separate targets in FunctionalTest.props to make items available during (now separate) Publish

nits:
- touch up RunHelix.ps1 console output
- reorder command line arguments for consistency in changed parts of the YAML files
- move `NoBuild=true` setting out of FunctionalTestWithAssets.props
- use `BeforeTargets` in FunctionalTest.props to improve determinism

Extension of https://github.com/dotnet/aspnetcore/pull/39898