Update internal build image

[akoeplinger]

The build.windows.10.amd64.vs2019 image doesn't exist anymore, it was replaced by windows.vs2019.amd64

[akoeplinger]

note that this also affects release/6.0 and release/7.0 branches so it should probably be backported

[dreddy-work]

@akoeplinger , what about pool name? I see following in 6.0 vs main in windows-build.yml. Also, its hard to track when the pool names and images are changing. Is there any central team or place to track on these changes?

   ${{ if eq(variables['System.TeamProject'], 'public') }}:
        name: NetCore-Svc-Public
        demands: ImageOverride -equals windows.vs2019.amd64.open
      ${{ if ne(variables['System.TeamProject'], 'public') }}:
        name: NetCore1ESPool-Svc-Internal
        demands: ImageOverride -equals windows.vs2019.amd64

vs

   ${{ if eq(variables['System.TeamProject'], 'public') }}:
        vmImage: 'windows-2019'
      ${{ if ne(variables['System.TeamProject'], 'public') }}:
        name: NetCore1ESPool-Internal
        demands: ImageOverride -equals windows.vs2019.amd64

[akoeplinger]

You can subscribe to the dncpartners@ list where dnceng posts these types of changes. As far as I know every team is reponsible to apply the changes.

As for the pool names: the vmImage: windows-2019 means it is a public pool not managed by 1ES but by AzDO, you can use it for public builds.

For internal builds the main branch should use NetCore1ESPool-Internal while release or servicing branches should use NetCore1ESPool-Svc-Internal (mainly for budgeting/reporting reasons).