(packer-images): Add Win-19, Win-22 (AMD64 and ARM64) AMIs For EC2 agents

[jayfranco999]

Due to the complexity of this PR – jenkins-infra/packer-images#1430

We are splitting the tasks into 4 stages, this issue is related to adding Win-19, Win-22 (AMD64 and ARM64) AMIs for our jenkins EC2 agents.

We are reintroducing the amazon logic that we were using with our previous AWS jenkins account – jenkins-infra/packer-images#734

• Include EC2 source for build-jenkins-agent-windows.pkr.hcl
• Add datasources.pkr.hcl to look-up windows-2019 and windows-2022 AMI ids for respective architecture
• Define windows_winrm_user in locals.pkr.hcl as administrator for amazon-ebs since admin permissions are required to ssh our windows ec2 agents
• Define all the common settings for AWS base image AMI's in sources.pkr.hcl

Originally posted by @jayfranco999 in #4316 (comment)

[github-actions]

Take a look at these similar issues to see if there isn't already a response to your problem:

1. 74% (packer-images): Add Linux AMD64 and ARM64 AMIs For EC2 agents #4353

[dduportal]

• The PR feat(windows) add AWS EC2 builds (2019 and 2022) packer-images#1611 did add the 2 AWS EC2 templates for Windows
• The release https://github.com/jenkins-infra/packer-images/releases/tag/2.18.0 now provides 2 new AMIs

[dduportal]

Note: we chose to use public IP with WinRM allowed to anywhere from Azure infra.ci agents.