Azure deployment needs updating.

It looks like there may have been significant changes to both the boundary provider as well as the azurerm provider. When running `terraform validate` in the deployment/azure directory, it returns the following Errors and Warnings:
```
Warning: Argument is deprecated

with module.azure.azurerm_lb_rule.controller,
on azure/lb.tf line 74, in resource "azurerm_lb_rule" "controller":
74: backend_address_pool_id = azurerm_lb_backend_address_pool.pools["controller"].id

This property has been deprecated by `backend_address_pool_ids` and will be removed in the next major version of the provider

(and 7 more similar warnings elsewhere)

Warning: Deprecated Resource

with module.boundary.boundary_host_catalog.backend_servers,
on boundary/hosts.tf line 1, in resource "boundary_host_catalog" "backend_servers":
1: resource "boundary_host_catalog" "backend_servers" {

Deprecated: use `resource_host_catalog_static` instead.

(and 2 more similar warnings elsewhere)

Error: Unsupported argument

on boundary/targets.tf line 8, in resource "boundary_target" "backend_servers_ssh":
8: host_set_ids = [

An argument named "host_set_ids" is not expected here.

Error: Unsupported argument

on boundary/targets.tf line 20, in resource "boundary_target" "backend_servers_website":
20: host_set_ids = [

An argument named "host_set_ids" is not expected here.
```

Perhaps the `host_set_ids` is really supposed to be `host_source_ids`?

Thanks

Run `terraform validate` in deployment/azure and inspect the reported resources in azure/lb.tf, boundary/hosts.tf, and boundary/targets.tf. Check the current provider documentation for the deprecated arguments and resources, then verify that validation completes without errors or deprecation warnings.

Written by the indexing model from the issue text.