Add replication regions to Azure job

[peterdeme]

Description of the change

Currently, our customers use these regions for their workers. We can add more later.

Type of change

• Bug fix (non-breaking change that fixes an issue);
• New feature (non-breaking change that adds functionality);
• Breaking change (fix or feature that would cause existing functionality to not work as expected);
• Documentation (a documentation or example fix not affecting the infrastructure managed by this module);

Checklists

Development

• All necessary variables have been defined, with defaults if applicable;
• The HCL code is formatted;
• An AMI has been created in some AWS account, and the AMI is working as expected;

Code review

• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached;
• This pull request is no longer marked as "draft";
• Reviewers have been assigned;
• Changes have been reviewed by at least one other engineer;

[peterdeme]

A target region to store the image version in. The attribute supersedes replication_regions which is now considered deprecated. One or more target_region blocks can be specified for storing an imager version to various regions. In addition to specifying a region, a DiskEncryptionSetId can be specified for each target region to support multi-region disk encryption. At a minimum their must be one target region entry for the primary build region where the image version will be stored. Target region must only contain one entry matching the build region when using shallow replication.

[adamconnelly]

Looks good. Just noticed something related to the target region blocks.