Port TLS Provider to terraform-plugin-framework

[detro]

Closes #196
Closes #87
Closes #185
Closes #174

This is a full port of the terraform-tls-provider to the new, and almost v1.x, terraform-plugin-framework.

As it is a breaking change (version of TF <0.15 become not compatible with this provider), I'm taking this opportunity to include other breaking changes that had been waiting for a while. Some of which (like #87), are long overdue and made necessary by the new framework, not supporting certain things (StateFunc in Schema definition).

The CHANGELOG contains all the details.

NOTES:

• Provider has been re-written using the new terraform-plugin-framework (#215).

BREAKING CHANGES:

• Terraform >=0.15 is now required to use this provider.

• resource/tls_cert_request: Attribute key_algorithm is now computed, as it's inferred from private_key_pem (#174, #215).

• resource/tls_self_signed_cert: Attribute key_algorithm is now computed, as it's inferred from private_key_pem (#174, #215).

• resource/tls_self_signed_cert: Setting an unsupported value in allowed_uses attribute, will now return an error instead of just a warning (#185, #215).

• resource/tls_locally_signed_cert: Attribute private_key_pem is stored (and returned) as-is (in accordance with guidelines) (#87, #215).

• resource/tls_locally_signed_cert: Attribute ca_key_algorithm is now computed, as it's inferred from ca_private_key_pem (#174, #215).

• resource/tls_locally_signed_cert: Setting an unsupported value in allowed_uses attribute, will now return an error instead of just a warning (#185, #215).

• resource/tls_locally_signed_cert: Attributes cert_request_pem, ca_private_key_pem, ca_cert_pem, private_key_pem are stored (and returned) as-is (in accordance with guidelines) (#87, #215).

• provider: HTTP proxy configuration is now a (nested) Attribute (proxy = {...), not a Block (proxy { ...) (#215).

[bendbennett]

Looking great!

[bendbennett]

Looking really good. I'm definitely going to re-use some of your ideas.

[bendbennett]

Nice! Looks great.

[bflad]

Overall this looks really good, nice work migrating this non-trivial provider! 🚀

[dpkirchner]

If we upgrade to the latest tls provider (4.0.4), and we bump in to issue #87, will applying cause all of our certificates to be replaced or will the update be a no-op? I'm using a fork of the tls provider to workaround #87 but I'm looking in to moving back to the main branch, however I can't have the plan replace the certificates spuriously.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.