Resource mapping file will now be generated together with the import.tf that is the TF plannable import blocks

[magodo]

The -g and s generates both a JSON versioned resource mapping file and the import.tf that is the new TF plannable import blocks, e.g.

>  cat import.tf
import {
  id = "/subscriptions/xxxx/resourceGroups/AZTFY-VMDISK/providers/Microsoft.Compute/virtualMachines/aztfy-test/extensions/Microsoft.Azure.Monitor.AzureMonitorLinuxAgent"
  to = azurerm_virtual_machine_extension.res-0
}
import {
  id = "/subscriptions/xxxx/resourceGroups/AZTFY-VMDISK/providers/Microsoft.Compute/virtualMachines/aztfy-test/extensions/Microsoft.Azure.Security.Monitoring.AzureSecurityLinuxAgent"
  to = azurerm_virtual_machine_extension.res-1
}

#...

Users are welcome to grab the import.tf and proceed the plannable import process for another importing experience that is provided by TF official.

This behavior only takes effect when the terraform under used is >= v1.5.0.

The generated import.tf is not really working, see: hashicorp/terraform#33201

@stemaMSFT The document in MS Doc needs to be updated once this PR is merged...

[stemaMSFT]

LGTM. Terraform 1.5 doesn't GA until July I believe, so I will need to talk to HashiCorp to get their thoughts on when exactly they believe it'd be ok for us to publish this update.

[magodo]

@stemaMSFT Since Terraform v1.5 is published, shall we merge this PR now?

[stemaMSFT]

@magodo merged!