WCR API about Image Super Resolution failed in Intel/AMD/QC platform

Nobody has claimed this yet.

<!--table
{mso-displayed-decimal-separator:"\.";
mso-displayed-thousand-separator:"\,";}
@page
{margin:.75in .7in .75in .7in;
mso-header-margin:.3in;
mso-footer-margin:.3in;}
.font5
{color:windowtext;
font-size:9.0pt;
font-weight:400;
font-style:normal;
text-decoration:none;
font-family:新細明體, serif;
mso-font-charset:136;}
tr
{mso-height-source:auto;
mso-ruby-visibility:none;}
col
{mso-width-source:auto;
mso-ruby-visibility:none;}
br
{mso-data-placement:same-cell;}
td
{padding:0px;
mso-ignore:padding;
color:black;
font-size:12.0pt;
font-weight:400;
font-style:normal;
text-decoration:none;
font-family:新細明體, serif;
mso-font-charset:136;
mso-number-format:General;
text-align:general;
vertical-align:middle;
border:none;
mso-background-source:auto;
mso-pattern:auto;
mso-protection:locked visible;
white-space:nowrap;
mso-rotate:0;}
.xl65
{font-family:Calibri, sans-serif;
mso-font-charset:0;
border-top:1.0pt solid windowtext;
border-right:1.0pt solid windowtext;
border-bottom:1.0pt solid windowtext;
border-left:none;
background:#E4F4DF;
mso-pattern:black none;
white-space:normal;}
.xl66
{font-family:Calibri, sans-serif;
mso-font-charset:0;
border-top:none;
border-right:1.0pt solid windowtext;
border-bottom:none;
border-left:none;
background:#C9FAFC;
mso-pattern:black none;
white-space:normal;}
.xl67
{font-family:Calibri, sans-serif;
mso-font-charset:0;
border-top:1.0pt solid windowtext;
border-right:1.0pt solid windowtext;
border-bottom:none;
border-left:none;
background:#C8E2FB;
mso-pattern:black none;
white-space:normal;}
.xl68
{font-family:Calibri, sans-serif;
mso-font-charset:0;
border:1.0pt solid windowtext;
background:#C8E2FB;
mso-pattern:black none;
white-space:normal;}
.xl69
{font-family:Calibri, sans-serif;
mso-font-charset:0;
border-top:none;
border-right:none;
border-bottom:1.0pt solid windowtext;
border-left:1.0pt solid windowtext;
background:#CAEABF;
mso-pattern:black none;
white-space:normal;}
.xl70
{font-family:Calibri, sans-serif;
mso-font-charset:0;
border:1.0pt solid windowtext;
background:#CAEABF;
mso-pattern:black none;
white-space:normal;}
.xl71
{font-family:Calibri, sans-serif;
mso-font-charset:0;
border-top:none;
border-right:none;
border-bottom:1.0pt solid windowtext;
border-left:none;
background:#CAEABF;
mso-pattern:black none;
white-space:normal;}
ruby
{ruby-align:left;}
rt
{color:windowtext;
font-size:9.0pt;
font-weight:400;
font-style:normal;
text-decoration:none;
font-family:新細明體, serif;
mso-font-charset:136;
mso-char-type:none;
display:none;}
-->

NB | OS | CPU | Memory | NPU | GPU
-- | -- | -- | -- | -- | --
AMD | 24H2 (OS build 26120.3576) Windows 11 Pro | AMD Ryzen AI 9 HX 370 w/ Radeon 890M | 32GB | NPU Compute Accelerator Device | AMD Radeon™ 890M Graphics
Intel | 24H2 (OS build 26120.3585) Windows 11 Pro | Intel® Core™ Ultra 5 238V | 32GB | Intel® AI Boost | Intel® Arc™ 130V GPU (16GB)
Qualcomm | 24H2 (OS build 26120.3360) Windows 11 Pro | Snapdragon® Xlite - X1E78100 - Qualcomm® Oryon™ CPU | 32GB | Snapdragon® Xlite - X1E78100 - Qualcomm® Oryon™ NPU (16GB) | Qualcomm® Adreno™ X1-85 GPU (GB)

I tested three laptops with specifications listed in the table above and found that the Image Super Resolution function behaves differently across platforms.

On AMD and QC devices, the code stops at `if (!ImageScaler.IsAvailable())`, while on the Intel device, it stops at `_imageScaler = await ImageScaler.CreateAsync();`.

[Enhance_Image_WCRSample.zip](https://github.com/user-attachments/files/19481294/Enhance_Image_WCRSample.zip)

Start with the attached Enhance_Image_WCRSample.zip and reproduce the ImageScaler behavior on the listed AMD, Intel, and Qualcomm devices. Inspect the ImageScaler.IsAvailable() and ImageScaler.CreateAsync() entry points; the issue does not name source files, tests, or a completion criterion, so the expected cross-platform behavior needs clarification.

Written by the indexing model from the issue text.