feat(misconf): Add support for aws_ami

[simar7]

Description

Related issues

• Close #XXX

Related PRs

• #XXX
• #YYY

Remove this section if you don't have related PRs.

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[nikpivkin]

The AMI is related to EC2, so I think it should be in the ec2 package as a field of the EC2 structure.
The aws_ami data source searches the image against the criteria and returns the id of an already registered AMI, while the resource creates the AMI. The owners field is only specific to the data source and if in the future we want to add checks for the resource, we will need to distinguish between the data source and the resource. Should we rename this structure to something like RequestedAMI (first thing that came to mind)?
Also, there may be multiple AMI data sources declared in the configuration , so this field should be a list.