Update aspire manifest to 8.1.0 (dotnet#42364)

Author: akoeplinger

NuGet.config

@@ -22,6 +22,7 @@
     <add key="dotnet7-transport" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7-transport/nuget/v3/index.json" />
     <add key="dotnet8" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json" />
     <add key="dotnet8-transport" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8-transport/nuget/v3/index.json" />
+    <add key="dotnet8-workloads" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8-workloads/nuget/v3/index.json" />
     <add key="dotnet9" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json" />
     <add key="dotnet9-transport" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9-transport/nuget/v3/index.json" />
     <add key="dotnet-public" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json" />

eng/Version.Details.xml

@@ -634,22 +634,22 @@
       <SourceBuild RepoName="scenario-tests" ManagedOnly="true" />
     </Dependency>
     <!--
-      Aspire isn't really a toolset dependency. However, it only inserts a baseline manifest in installer,
-      and if you squint at it, this means we can say that its specific dependency versions don't matter to installer.
+      Aspire isn't really a toolset dependency. However, it only inserts a baseline manifest in sdk,
+      and if you squint at it, this means we can say that its specific dependency versions don't matter to sdk.
       It also doesn't currently ship 9.0 preview versions, meaning the version is locked to the latest shipped from 8.0 era.
-      Avoiding this as a product dependency avoids a long coherency path (aspnetcore->extensions->aspire->installer).
+      Avoiding this as a product dependency avoids a long coherency path (aspnetcore->extensions->aspire->sdk).
       **It is** of course possible that an incoherent aspire means that aspire depends on versions of extensions that
       aren't shipping, or those extensions packages depend on aspnetcore packages that won't ship. However, given the cost
       of maintaining this coherency path is high. This being toolset means that aspire is responsible for its own coherency.
     -->
-    <Dependency Name="Microsoft.NET.Sdk.Aspire.Manifest-8.0.100" Version="8.0.1">
+    <Dependency Name="Microsoft.NET.Sdk.Aspire.Manifest-8.0.100" Version="8.1.0">
       <Uri>https://github.com/dotnet/aspire</Uri>
-      <Sha>a6e341ebbf956bbcec0dda304109815fcbae70c9</Sha>
+      <Sha>d304c5f6f15bcd4f34f1841b33870cfab88e6937</Sha>
     </Dependency>
     <!-- Intermediate is necessary for source build. -->
-    <Dependency Name="Microsoft.SourceBuild.Intermediate.aspire" Version="8.0.1-preview.8.24267.1">
+    <Dependency Name="Microsoft.SourceBuild.Intermediate.aspire" Version="8.1.0-preview.1.24373.2">
       <Uri>https://github.com/dotnet/aspire</Uri>
-      <Sha>a6e341ebbf956bbcec0dda304109815fcbae70c9</Sha>
+      <Sha>d304c5f6f15bcd4f34f1841b33870cfab88e6937</Sha>
       <SourceBuild RepoName="aspire" ManagedOnly="true" />
     </Dependency>
   </ToolsetDependencies>

eng/Versions.props

@@ -346,7 +346,7 @@
   </PropertyGroup>
   <PropertyGroup Label="Workload manifest package versions">
     <AspireFeatureBand>8.0.100</AspireFeatureBand>
-    <MicrosoftNETSdkAspireManifest80100PackageVersion>8.0.1</MicrosoftNETSdkAspireManifest80100PackageVersion>
+    <MicrosoftNETSdkAspireManifest80100PackageVersion>8.1.0</MicrosoftNETSdkAspireManifest80100PackageVersion>
     <MauiFeatureBand>9.0.100-preview.6</MauiFeatureBand>
     <MauiWorkloadManifestVersion>9.0.0-preview.6.24327.7</MauiWorkloadManifestVersion>
     <XamarinAndroidWorkloadManifestVersion>34.99.0-preview.6.340</XamarinAndroidWorkloadManifestVersion>