Terminator policies for CloudFront modules

[abikouo]

Needed for PR ansible-collections/community.aws#1596

[gravesm]

Could you add the link in the description to the PR in the amazon collection that this change is for?

[abikouo]

Could you add the link in the description to the PR in the amazon collection that this change is for?

PR has been updated accordingly

[jillr]

Apologies I missed some of this on my previous look.
The policies are in paas.yml but the terminator class is in application-services.py - these should be in the same grouping in both places to avoid confusion.

There may be a bug in the plugin code, the integration tests fail at:

TASK [cloudfront_distribution : Update the distribution with tags] **************************************************************************************************************************************************************************
task path: /root/ansible_collections/community/aws/tests/output/.tmp/integration/cloudfront_distribution-5u0dnd61-ÅÑŚÌβŁÈ/tests/integration/targets/cloudfront_distribution/tasks/main.yml:34
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: get_distribution() got an unexpected keyword argument 'id'
fatal: [testhost]: FAILED! => {"boto3_version": "1.18.0", "botocore_version": "1.21.0", "changed": false, "msg": "Error validating distribution_id from alias, aliases and caller reference: get_distribution() got an unexpected keyword argument 'id'", "resource_actions": []}

I have the policies deployed to the dev area of the CI account (with all of the policies moved to a ResourceUnrestricted Sid for the sake of testing). You can test your PR locally against the CI account like ansible-test integration -vv cloudfront_distribution --remote-stage dev --docker with the deployed dev policy. We can figure out the resource restrictions in another iteration.