xz_utils: honor static runtime for clang-cl

[SpaceIm]

Summary

Changes to recipe: lib/[version]

Motivation

In case of a profile representing clang-cl with static runtime, runtime is not honored. This PR fixes it.

Details

see #25014 (comment)

---

• Read the contributing guidelines
• Checked that this PR is not a duplicate: list of PRs by recipe
• Tested locally with at least one configuration using a recent version of Conan

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 1 (51a52796c0950166285623a0652acb445a417861):

• xz_utils/5.4.5:
  All packages built successfully! (All logs)

• xz_utils/5.4.0:
  All packages built successfully! (All logs)

• xz_utils/5.4.4:
  All packages built successfully! (All logs)

• xz_utils/5.2.5:
  All packages built successfully! (All logs)

• xz_utils/5.4.2:
  All packages built successfully! (All logs)

• xz_utils/5.2.10:
  All packages built successfully! (All logs)

• xz_utils/5.2.4:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 1 (51a52796c0950166285623a0652acb445a417861):

• xz_utils/5.4.5:
  All packages built successfully! (All logs)

• xz_utils/5.4.0:
  All packages built successfully! (All logs)

• xz_utils/5.4.2:
  All packages built successfully! (All logs)

• xz_utils/5.2.5:
  All packages built successfully! (All logs)

• xz_utils/5.2.10:
  All packages built successfully! (All logs)

• xz_utils/5.2.4:
  All packages built successfully! (All logs)

• xz_utils/5.4.4:
  All packages built successfully! (All logs)

[jcar87]

runtime is not honored.

For this profile and without changes from this PR:

Profile host:
[settings]
arch=armv8
build_type=Release
compiler=clang
compiler.cppstd=17
compiler.runtime=static
compiler.runtime_type=Release
compiler.runtime_version=v144
compiler.version=17
os=Windows
[conf]
tools.cmake.cmaketoolchain:generator=Visual Studio 17

I can se the /MT flag being passed correctly (and the test package passing, otherwise I imagine it would fail with the mismatch)

The /MT flag is correctly set by the Conan-generated .props - so while it is building the pre-existing configuration that doesn't have MT in the name - it is actually correctly obeying the Conan-passed settings - may be that the solution here is to just disregard that block altogether