SHIR Image appears to be amd64, error from this project trying to build x84

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [ X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
> Simply deploy the solution as directed in the readme: https://github.com/Azure-Samples/azure-data-factory-runtime-app-service#deploy-and-test-the-sample

### Any log messages given by the failure
Error in the ACR Build Task:
> 2023/10/23 19:58:46 Downloading source code...
2023/10/23 19:58:53 Finished downloading source code
2023/10/23 19:58:54 Using acb_vol_93f05fe4-c160-4fb4-b824-faa8c239cd27 as the home volume
2023/10/23 19:58:54 Setting up Docker configuration...
2023/10/23 19:59:01 Successfully set up Docker configuration
2023/10/23 19:59:01 Logging in to registry: shirisyh2d2aj45ei.azurecr.io
2023/10/23 19:59:04 Successfully logged into shirisyh2d2aj45ei.azurecr.io
2023/10/23 19:59:04 Executing step ID: build. Timeout(sec): 28800, Working directory: '', Network: ''
2023/10/23 19:59:04 Scanning for dependencies...
2023/10/23 19:59:07 Successfully scanned dependencies
2023/10/23 19:59:07 Launching container with name: build
Sending build context to Docker daemon 92.67kB

> Step 1/7 : FROM mcr.microsoft.com/windows/servercore:ltsc2019
ltsc2019: Pulling from windows/servercore
cb524f6f2215: Already exists
717cc7e60494: Pulling fs layer
717cc7e60494: Verifying Checksum
717cc7e60494: Download complete
717cc7e60494: Pull complete
Digest: sha256:b3b5f1d43d7004541aae6f0c2ead0c70d943c85653f0e37861c73eaa9d687c42
Status: Downloaded newer image for mcr.microsoft.com/windows/servercore:ltsc2019

> WARNING: Pulled image with specified platform (windows/x86), but the resulting image's configured platform (windows/amd64) does not match.
This is most likely caused by a bug in the build system that created the fetched image (mcr.microsoft.com/windows/servercore:ltsc2019).
Please notify the image author to correct the configuration.
---> 87e42ae65ff1
Step 2/7 : ARG INSTALL_JDK=false
---> Running in d88a5a7240d2
Removing intermediate container d88a5a7240d2
---> 9e47e3d00306
Step 3/7 : COPY SHIR C:/SHIR/
failed to get destination image "sha256:9e47e3d00306684f0bdaccde2ecbb2691ccf52748003fe3743d299a2a0c83422": image with reference sha256:9e47e3d00306684f0bdaccde2ecbb2691ccf52748003fe3743d299a2a0c83422 was found but does not match the specified platform: wanted windows/x86, actual: windows/amd64
2023/10/23 20:00:32 Container failed during run: build. No retries remaining.
failed to run step ID: build: exit status 1
Run ID: ca1 failed after 1m48s. Error: failed during run, err: exit status 1

### Expected/desired behavior
> Should we expect the container to build as-is? When I manually change to amd64 in the acr.bicep module, this will build successfully. Should this solution be updated to support amd64?

### Mention any other details that might be useful

> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

Start with the README deployment instructions and the acr.bicep module, focusing on the architecture setting used by the ACR Build Task. Reproduce the deployment and verify that the image builds without the windows/x86 versus windows/amd64 platform mismatch; done means the solution builds successfully for amd64.

Written by the indexing model from the issue text.