Visual Studio Toolkit Fails to Deploy .NET Applications to ARM64 ECS Containers Due to Missing --load Option in Docker Buildx Command

**Describe the bug**
Summery: Visual Studio Toolkit Fails to Deploy .NET Applications to ARM64 ECS Containers Due to Missing --load Option in Docker Buildx Command

Description:
When using the Visual Studio Toolkit to deploy a .NET application to an ARM64 ECS Container, the container build consistently fails. This issue occurs because the Docker image, specifically the ARM64 version, is not being properly loaded or made available after a successful build.
I am building Docker images on a remote Linux server (with Docker exposed via TCP) from a Windows Server machine, utilizing DOCKER_HOST environment variable for connectivity. While building and pushing an image in a single command works (with --push option), simply building an ARM64 image results in the following warning:
`WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load`

This indicates that the built image only resides in the build cache and is not loaded into Docker for subsequent use, unless the --load option is explicitly used.

The Visual Studio Toolkit's generated docker buildx build command, shown below, is missing this crucial --load option:

docker buildx build --platform linux/arm64 -t bookstoreweb:638881127934052892 -f "C:\code\bobs-used-bookstore-classic\app\Bookstore.Web\Dockerfile" .

**To Reproduce**
Build any image after selecting "Environment Architecture" as Arm64 in Publish to AWS dialog box.

**Expected behavior**
The toolkit should be able to create arm64 image and load it to current context so that it can be used by subsequent commands.

**Screenshots**

**Toolkit Logs**

Not Required

**Development System (please complete the following information):**
- Windows Version: Windows Server 2019
- Visual Studio Version: 2022
- AWS Toolkit for Visual Studio Version: 1.74.0.0 (AWS Toolkit with Amazon Q)

**Additional context**
NA

Start from the Publish to AWS dialog's generated Docker Buildx command for the ARM64 environment and compare it with the command shown in the issue. Verify that the resulting image is loaded into the current Docker context and that a subsequent ARM64 ECS deployment succeeds; the issue is done when this workflow works without the cache-only warning.

Written by the indexing model from the issue text.