[main] Update dependencies from dnceng/internal/dotnet-optimization

[dotnet-maestro]

This pull request updates the following dependencies

Coherency Updates

The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format

• Coherency Updates:
  • Microsoft.SourceLink.GitHub: from 8.0.0-beta.23252.2 to 8.0.0-beta.23218.3 (parent: Microsoft.DotNet.Arcade.Sdk)
  • Microsoft.DotNet.XliffTasks: from 1.0.0-beta.23266.1 to 1.0.0-beta.23263.1 (parent: Microsoft.DotNet.Arcade.Sdk)

From https://dev.azure.com/dnceng/internal/_git/dotnet-optimization

• Subscription: d3a5b203-1393-4534-5b62-08d8d8feb47e
• Build: 20230521.4
• Date Produced: May 22, 2023 6:20:28 AM UTC
• Commit: 85af145192ce699ffcc16bd1a7b565820b6a2dff
• Branch: refs/heads/main

• Updates:
  • optimization.linux-arm64.MIBC.Runtime: from 1.0.0-prerelease.23260.3 to 1.0.0-prerelease.23271.4
  • optimization.linux-x64.MIBC.Runtime: from 1.0.0-prerelease.23260.3 to 1.0.0-prerelease.23271.4
  • optimization.windows_nt-arm64.MIBC.Runtime: from 1.0.0-prerelease.23260.3 to 1.0.0-prerelease.23271.4
  • optimization.windows_nt-x64.MIBC.Runtime: from 1.0.0-prerelease.23260.3 to 1.0.0-prerelease.23271.4
  • optimization.windows_nt-x86.MIBC.Runtime: from 1.0.0-prerelease.23260.3 to 1.0.0-prerelease.23271.4
  • optimization.PGO.CoreCLR: from 1.0.0-prerelease.23260.3 to 1.0.0-prerelease.23271.4

[lewing]

cc @dotnet/source-build-contrib

[MichaelSimons]

@oleksandr-didyk please take a look at the prebuilts. Why were the sourcelink and xliff-tasks versions incoherent with arcade and where do the prebuilts come from?

[oleksandr-didyk]

@oleksandr-didyk please take a look at the prebuilts. Why were the sourcelink and xliff-tasks versions incoherent with arcade and where do the prebuilts come from?

The pre-builts appear since they are dependencies from the referenced version of Arcade, i.e. they were coherent before this change.

I have no idea why Maestro did this downgrade nor can I reproduce it locally. I'll try asking around, but for now it seems just reverting the downgrade would solve the pre-builts

[sbomer]

With the latest updates this is getting the new profile data format produced by https://dev.azure.com/dnceng/internal/_git/dotnet-optimization/pullrequest/31410. As expected, the innerloop build was failing with:

error: Could not read profile /__w/1/s/.packages/optimization.linux-x64.pgo.coreclr/1.0.0-prerelease.23270.4/data/coreclr.profdata: unsupported instrumentation profile format version

I pushed a fix for #85785 that should unblock this. @janvorli @jkoritzinsky PTAL.

[sbomer]

I tried reverting the coherency downgrades as suggested in #86436 (comment).