[RPD-279] [BUG] Automatically deal with stale states

[Christopher-Norman]

This bug is recreated by allowing the state storage to be provisioned and stopping the program before reaching the AKS and other resources provisioning. This meant that the matcha.state file looks similar to:

{
    "cloud": {
        "prefix": "test",
        "location": "uksouth",
    }
}

Which does not include resource-group-name hence when we try to access this value to check if the matcha state is stale
we get an error that the value does not exist.
Instead the matcha.state file needs to be:

{
    "cloud": {
        "prefix": "test",
        "location": "uksouth",
        "resource-group-name": "test-resources"
    }
}

After the resource group and state storage is provisioned.

This bug can happen if there is something wrong with the resources Terraform and the Terraform init/apply fails causing matcha to halt halfway through provisioning.

To fix this we add the resource group name to matcha.state file after provisioning the remote state rg and storage.

Checklist

Please ensure you have done the following:

• I have read the CONTRIBUTING guide.
• I have updated the documentation if required.
• I have added tests which cover my changes.

Type of change

Tick all those that apply:

• Bug Fix (non-breaking change, fixing an issue)
• New feature (non-breaking change to add functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[JonoCX]

Nice! 🐛