Revisit/test common controller after final tfcli implementation

[turkenh]

What problem are you facing?

The common controller is a layer sitting between generated schema and async terraform CLI library, mostly dealing with conversions between crossplane/terraform and proper implementation of crossplane managed reconciler interface functions.

The current implementation is mostly tested with some early implementations (open PRs, assumptions) and happy path scenarios (mostly with AWS VPC).

How could Terrajet help solve your problem?

We would need to revisit the existing implementation with more resources and edge-case scenarios.
Another point is, implementation of this layer could be affected by the output of this discussion, hence it might make sense to consider that while working here.

[ulucinar]

I have tested successfully CRUD operations using common controller on top of #3.

Albeit somewhat slow (because we are waiting for terraform, and because we are not polling frequent enough), I have been successfully provision an AWS VPC, observe it in ready state, update its tags, and delete it via its MR.

[turkenh]

Closing in favor of #55