Use CloudFormation Resource Providers

Why not use Resource Type Providers (Python [here](https://github.com/aws-cloudformation/cloudformation-cli-python-plugin/)) instead of custom resources? If the resource types are split into smaller parts, other deployment frameworks (like [CDK](https://docs.aws.amazon.com/cdk/api/latest/), [Terraform](https://www.terraform.io/docs/providers/aws/index.html), [Pulumi](https://www.pulumi.com/docs/), [OrgFormation](https://github.com/OlafConijn/AwsOrganizationFormation)) could use them to manage AWS resources. The benefit being the ability to share code among all of them because we will be using CloudFormation services in the end.

The issue names no repository files, tests, or implementation entry points. Start by reviewing the current custom-resource implementation, then compare it with CloudFormation Resource Type Providers and the linked CDK, Terraform, Pulumi, and OrgFormation integrations. Done requires an agreed scope, resource split, and acceptance criteria.

Written by the indexing model from the issue text.