feat(misconf): Update Azure network schema for new checks

[yagreut]

Update Azure network schema for new checks:

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[nikpivkin]

Hi @yagreut !

Currently, searching for related resources is not implemented for ARM templates, unlike Terraform and CloudFormation. In this PR, I suggest adding the adaptation only for Terraform. I’ll review soon whether it’s possible to implement related resource search for ARM — at the moment, the parser cannot evaluate expressions and, as far as I remember, has no concept of references.

[github-actions]

📊 API Changes Detected

Semver impact: major

github.com/aquasecurity/trivy/pkg/iac/providers/azure/compute
  Incompatible changes:
  - LinuxVirtualMachine.NetworkInterfaces: changed from []NetworkInterface to []github.com/aquasecurity/trivy/pkg/iac/providers/azure/network.NetworkInterface
  - NetworkInterface: removed
  - VirtualMachine.NetworkInterfaces: changed from []NetworkInterface to []github.com/aquasecurity/trivy/pkg/iac/providers/azure/network.NetworkInterface
  - WindowsVirtualMachine.NetworkInterfaces: changed from []NetworkInterface to []github.com/aquasecurity/trivy/pkg/iac/providers/azure/network.NetworkInterface

github.com/aquasecurity/trivy/pkg/iac/adapters/terraform/azure/network
  Compatible changes:
  - AdaptNetworkInterface: added

github.com/aquasecurity/trivy/pkg/iac/providers/azure/network
  Compatible changes:
  - IPConfiguration: added
  - Network.NetworkInterfaces: added
  - NetworkInterface: added
  - NetworkWatcherFlowLog.Enabled: added

[nikpivkin]

We have two options for handling the network interface in ARM:

• Option 1:
  If you do not plan to add checks that require the presence of a network interface, for example:

  count(compute.networkinterfaces) == 0
  result.new("Compute instance must have at least one network interface", ...)

  we can simply skip adding them during parsing.

• Option 2: Otherwise, we should create metadata via NewUnmanagedMetadata(), so that we can skip unmanaged networks in checks, for example:

  some ni in compute.networkinterfaces
  isManaged(ni)

Personally, I prefer Option 1, but I’m not sure how these interfaces will be used.