AWS::Config::DeliveryChannel / ConfigurationRecorder-Support import operations

## 1. AWS::Config::DeliveryChannel/ConfigurationRecorder-Support import operations

## 2. Scope of request

Currently these resources are not supported from being imported into CloudFormation stacks.

There is a limit of one of each resource per region/account, which makes it convenient to import these resources instead of having to remove/re-create them.

## 3. Expected behavior

Imported operations should be possible for AWS::Config::DeliveryChannel and AWS::Config::ConfigurationRecorder resources

## 4. Suggest specific test cases

Import existing instances of these resources on a new CloudFormation stack

## 5. Helpful Links to speed up research and evaluation

- [List of supported resources that support import operations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/resource-import-supported-resources.html)
- [AWS::Config::DeliveryChannel](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-config-deliverychannel.html)
- [AWS::Config::ConfigurationRecorder](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-config-configurationrecorder.html)

## 6. Category (required) - Will help with tagging and be easier to find by other users to +1

5. Management (CloudTrail, Config...)

Start by reviewing the linked list of CloudFormation resources that support import operations and the AWS::Config::DeliveryChannel and AWS::Config::ConfigurationRecorder documentation. Reproduce importing existing instances of both resources into a new CloudFormation stack, then add or run coverage for those import operations and verify that each resource imports successfully.

Written by the indexing model from the issue text.