Windows Container task is created with wrong networking mode

Windows Container task is created with wrong networking mode

## Expected Behavior
Windows container task should be created with "default" networking mode.

## Current Behavior
When using option “Publish Container to AWS…” for Windows container project project the task is being created with the WRONG (incompatible) networking mode: "Bridge" instead of required "default" for Windows containers

## Possible Solution
Change template for configuring task for Windows containers.

## Steps to Reproduce (for bugs)
Use “Publish Container to AWS…” for Windows container project project in "AWS Toolkit for Visual Studio" and then review the networking mode of the task created.

## Context
Affects advertised functionality to publish containers to AWS using toolkit.

## Your Environment
* Server 2016 AWS AMI
* VS 2017, VS 2019
* .Net Core 2.1

## .NET Core Info

[logging]: http://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/net-dg-config-other.html

Start by locating the task template used by the AWS Toolkit for Visual Studio's “Publish Container to AWS…” flow for Windows containers. Compare the networking mode selected for Windows and non-Windows tasks, then reproduce the publish flow and verify that the created Windows task uses "default" rather than "Bridge" networking.

Written by the indexing model from the issue text.