[bug] Qhub Azure deploy fails when remote state is activated

[viniciusdc]

Describe the bug

According to some recent intagration tests logs, it seems that qhub is trying to create two resource groups with the same name, resulting in the error below:

[terraform]: azurerm_resource_group.resource_group: Creating...
[terraform]: ╷
[terraform]: │ Error: A resource with the ID "/subscriptions/***/resourceGroups/<rg-name>" already exists - to be managed via Terraform this resource needs to be imported into the State. Please see the resource documentation for "azurerm_resource_group" for more information.
[terraform]: │ 
[terraform]: │   with azurerm_resource_group.resource_group,
[terraform]: │   on main.tf line 1, in resource "azurerm_resource_group" "resource_group":
[terraform]: │    1: resource "azurerm_resource_group" "resource_group" {
[terraform]: │ 
[terraform]: ╵

the error seems to be caused by the presence of another resource group created during 01-terraform-state stage:

INFO:qhub.provider.terraform:terraform apply directory=stages/01-terraform-state/azure targets=[]
INFO:qhub.provider.terraform: terraform at /tmp/terraform/1.0.5/terraform
[terraform]: 
[terraform]: Terraform used the selected providers to generate the following execution
[terraform]: plan. Resource actions are indicated with the following symbols:
[terraform]:   + create
[terraform]: 
[terraform]: Terraform will perform the following actions:
[terraform]: 
[terraform]:   # module.terraform-state.azurerm_resource_group.terraform-resource-group will be created
[terraform]:   + resource "azurerm_resource_group" "terraform-resource-group" {
[terraform]:       + id       = (known after apply)
[terraform]:       + location = "eastus"
[terraform]:       + name     = "<rg-name>"
[terraform]:     }
...
[terraform]: module.terraform-state.azurerm_resource_group.terraform-resource-group: Creating...
[terraform]: module.terraform-state.azurerm_resource_group.terraform-resource-group: Creation complete after 1s [id=/subscriptions/***/resourceGroups/<rg-name>]

The possible solution here would be

• removing the resource group creation (and any possible duplicate resource) from the 01 stage -- this might not be feasible depending on the reason it was in there
• Using the new python dynamic system to overwrite the 02 stage to import the necessary resources to state using data

Expected behaviour

• A successeful deployment of an Azure qhub cluster

How to reproduce

• deploy qhub from main and initialize an Azure deployment with terraform-state=remote