Tier 3 - Workloads

[brooke-hamilton]

Benefit/Result/Outcome
A single tier is deployed and networked so that a workload can be hosted there.

Description
This issue describes the core setup of tier 3 - workloads. A Tier 3 is a container for one or more workloads within a vnet and related configuration and logging configuration.
Every deployment is additive - new vnets are created each time. Multiple T3 vnets can exist in the same subscription.
Peering among workloads is done via the hub.

The user interface is not include in the scope of this issue. It included in issue #168

Acceptance Criteria

• A separate deployment is available that sets up a tier 3, i.e. a separate script.
• All tier 3s include a VNet configured with peering.
• Logging is configured.
• Multiple T3s can be deployed into a single MLZ environment.
• Guidance/instructions/documentation on T3s and deployment is available, including modifying the main README to describe what a tier 3 is and how it is used.