[WIP] Implement local planner

[alexsomesan]

Description

Introduces a new method of generating the plan by extracting the type information for the resource being planned from the OpenAPI definition available on the API server.

This approach should generate a more complete resource structure, which enable more robust resource lifecycle as all attributes ar being accounted for throughout all operations.

It does not make dry run-calls to the API server during planning, which removes the limitation of not being able to plan resources that depend on one another.

Milestones:

[x] Synthesize Terraform native types from OpenAPI spec
[x] Type-morph the user-supplied resource attributes onto the OpenAPI scaffolding
[x] JSON to Terraform types serialization / deserialization following OpenAPI scaffolding
[ ] Resolve issues in type converter regarding IntOrString types and CRD OpenAPI embedded spec

Acceptance tests

• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch? (If so, please include the test log in a gist)

[FooBarWidget]

I need this feature. Is there anything I can do to speed this up?

[WilliamABradley]

@alexsomesan is this waiting for an upstream Terraform feature to progress?
Is there a PR in Terraform to track for this?

[aareet]

@WilliamABradley we are working on a significant upgrade of the provider to use the new provider development modules. This PR is blocked on that change. We're working to get it out the door asap.

[alexsomesan]

superseded by #151

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!