feat: consider new best practices

[mavogel]

General

• https://www.terraform.io/docs/extend/hashicorp-provider-design-principles.html
• https://github.com/hashicorp/terraform-provider-scaffolding
• https://blog.container-solutions.com/write-terraform-provider-part-1
• https://learn.hashicorp.com/tutorials/terraform/provider-use?in=terraform/providers
• https://www.terraform.io/docs/extend/index.html
• consider more best practices for sdk v2 like using the ExactlyOneOf property -> feat: consider new best practices #6
• the latest videos and https://www.youtube.com/watch?v=XlxkqXQCZ4Y
• consider https://github.com/radeksimko/terraform-gen

Other providers

• https://github.com/terraform-providers/terraform-provider-azurerm#developer-generating-resource-id-formatters-parsers-and-validators
• https://github.com/terraform-providers/terraform-provider-azurerm#developer-scaffolding-the-website-documentation

[github-actions]

This issue is stale because it has been open 60 days with no activity.
Remove stale label or comment or this will be closed in 7 days.
If you don't want this issue to be closed, please set the label pinned.

[Junkern]

I would consider this issue as outdated.
Hashicorp has released its new SDK (called plugin framework) 3 weeks ago: https://github.com/hashicorp/terraform-plugin-framework

It has some features which would come in handy for us (https://developer.hashicorp.com/terraform/plugin/which-sdk#do-you-need-more-features-than-sdkv2-provides).
I would think that some of the current open issues can be solved by the new features. So whenever we tackle one of those issues we migrate the resource/data source to the new framework