Ensure dependency order for Deploy artifacts

[AndyButland]

The issue raised that this should resolve is here, where it seems to matter whether or not a template had a master template defined or not as to whether you could successfully deploy content that uses it.

After a bit of digging I found that Deploy was reporting a schema mismatch between two template entities that were identical, due to differences in how the dependencies of the template were ordered within the serialized output. This wasn't reproducible between two local environments, only between local and Cloud.

Initially I thought we weren't ensuring the order and were relying on the collection to come back in a particular way, but actually we are doing this. However the difference in behaviour looks to be due to differences in globalization settings (as we've seen in other contexts, related to this).

I've been able to demonstrate that the ordering of the string representations of these two UDIs comes back one way locally, and the opposite way in Cloud:

  var dependencies = new List<string>
  {
      "umb://template/d4651496fad24c1290a53ea4d55d945b",
      "umb://template-file/TestPage.cshtml"
  };
  foreach(var dependency in dependencies.OrderBy(x => x, StringComparer.InvariantCultureIgnoreCase))
  {
      <div>@dependency</div>
  }

Using OrdinalIgnoreCase makes them consistent though in both environments. Hence I've applied the same setting for the ordering we do in core.

In the end think we've just been quite unlucky in having two entities that happen to be ordered by - v /.

[AndyButland]

I've tested this further by releasing the build from this PR as a nightly, updating my Cloud project to reference that, and can now transfer content for documents depending on a template that both has and doesn't have a master template.

[bergmania]

Thanks.. That issue is ugly :P

I'll merge this, but I think the right thing is to ensure the environments run using same globalization.
E.g. by using this

  <ItemGroup Condition="'$(OS)' == 'Windows_NT'">
    <PackageReference Include="Microsoft.ICU.ICU4C.Runtime" Version="68.2.0.6" />
    <RuntimeHostConfigurationOption Include="System.Globalization.AppLocalIcu" Value="68.2" />
  </ItemGroup>

in the csproj

[bergmania]

I also cherry picked for 9.0.1

[bjarnef]

@bergmania I added your suggestion #11265 (comment) to the UmbracoProject.csproj file and deployed to Cloud environment, but it didn't seem to make a difference.

I still get same mismatch errors, when transfer content from local to remote environment.

Maybe it also need the changes in this PR as well?

Update: A bit later it seemed to work and on subsequent transfers I haven't had these mismatch errors.

[bjarnef]

@AndyButland @bergmania could this be the cause to the issues I am facing with entityResource.getByIds(Udi[]) in MNTP since I am seeing this in v9.0.1 on Umbraco Cloud, but it worked in v9.0.0?

See #11448