Create application resource in framework

[hmlanigan]

Note - there are 2 acceptance tests failing right now, though I'm not sure why. I cannot reproduce outside of the

Description

Convert the application resource from using the terraform sdk to the newer framework. There is a small bug fix related to exposing an application without an application name specified in the plan.

This PR also adds use the tflog package for logging including using a tflog subsystem for granularity. Each resource and data source should have its own subsystem. For applications, log line will include "@module":"juju.resource-application". To setup: export TF_LOG_PROVIDER=TRACE ; export TF_LOG_PATH=./terraform.log. Without the log path, logging will be printed within the normal terraform output.

Includes a fix for:
#274 Provider panics when generating plan

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Maintenance work (repository related, like Github actions, or revving the Go version, etc.)

Environment

• Juju controller version: 2.9.43

• Terraform version: 0.8.0 next

QA steps

Here is a plan to test with. Also do import testing.

terraform {
  required_providers {
    juju = {
      version = ">= 0.7.0"
      source  = "juju/juju"
    }
  }
}

provider "juju" {
}

resource "juju_model" "testmodel" {
  name = "machinetest"
}

resource "juju_application" "application_example" {
  model = juju_model.testmodel.name
  charm {
    name = "juju-qa-test"
  }
  units = 2
  expose {}
  config = {
	status = "application resource testing"
        foo-file = true
        skill = 42
  }
}

Notes

JUJU-4175
JUJU-4500

[cderici]

This looks great, actually, big piece of work 💪 just need some small adjustments, and the tests need to be fixed. The QA was mostly good, bumped into that no name specified error, import worked well 👍

[hmlanigan]

@cderici I pushed some some changes based on review comments, then rebased onto #269.

[cderici]

This is essentially ready to go, though please fix the tests before merge.

I just re-ran the tests because I'm not getting the same errors locally, not sure if CI is outdated. Anyways, the QA went well, however, I'm getting the following error when I run TestAcc_ResourceApplication_sdk2_framework_migrate locally.

resource_application_test.go:17: Step 6/6 error running import: ImportStateVerify attributes not equivalent. Difference is shown below. The - symbol indicates attributes missing after import.

          map[string]string{
        -       "model": "tf-test-application-2356628633933833839",
        -       "name":  "test-app",
          }
--- FAIL: TestAcc_ResourceApplication_sdk2_framework_migrate (113.70s)

[hmlanigan]

@cderici if the tests don't pass, we should be able to merge. and the button isn't green for me.

[hmlanigan]

force pushed to fix a merge conflict

[hmlanigan]

squashed many of the commands for merging. the test failing due to a juju bug will be skipped for now and re-enabled when the bug is fixed.