feat: upgrade azure providers

[kirklandnuts]

Summary

We want to update our azurerm and azuread providers to >=4.0 and >=3.0, respectively. See ticket for context.

This required two changes:

1. azurerm 4.0 made subscription_id a required argument, so our regional modules (global == false) need to now reference the scanning_subscription_id from the global module reference.
2. azuread changed the expected parsing format of service_principal_id so it now requires a fully qualified id — we resolve this by referencing azuread_service_principal.data_loader[0].id instead of azuread_service_principal.data_loader[0].object_id

How did you test this change?

Successfully deployed an azure awls integration on prod-canary-test.lacework.net - was also able to destroy the integration successfully.

Issue

AWLS2-561

[kirklandnuts]

Hi @PengyuanZhao, I'm having some trouble with terraform-docs.

I ran make terraform-docs and it executed terraform-docs using docker:

$ make terraform-docs
make terraform-docs
scripts/terraform-docs.sh
## terraform-docs not found in PATH, but docker was found
## running terraform-docs in docker
data/README.md updated successfully

The README's md5 hash is 569a72d2967e32579f329917ca5ae9ce, which doesn't match the expected hash generated in the github workflow, 86072e01e369fec29bedb8cb19fdd7d1.

$ md5sum README.md   
569a72d2967e32579f329917ca5ae9ce  README.md

I even tried installing terraform-docs locally and am still having the same result:

$ terraform-docs --version
terraform-docs version v0.17.0 795d369 linux/amd64

$ terraform-docs .        
README.md updated successfully

$ md5sum README.md
569a72d2967e32579f329917ca5ae9ce  README.md

Here's my question: do you know why terraform-docs is generating a README in github workflow that's different from what terraform-docs is generating when I run it locally?

Am I doing something wrong?

[PengyuanZhao]

LGTM

[lokesh-vadlamudi]

LGTM :-)