provider/aws: AWS prefix lists to enable security group egress to a VPC Endpoint

[dtolnay]

This is a rebase of #6872. Fixes #3413 and closes #6872.

This PR is based on the following:

• Issue Ability for AWS Security Group to Associate AWS Prefix List ID #3413
• VPC Endpoint routing - AWS docs

In addition, one acceptance test is broken into two parts as one part requires EC2 Classic to operate.

The changes introduce two new concepts:

• prefix_list_id exported attribute on an aws_vpc_endpoint
• prefix_list_ids configuration options on aws_security_group/egress and aws_security_group_rule

All non-EC2 Classic acceptance tests in the security group and security group rule files are passing on my build. Other acceptance tests haven't been executed due to cost and time requirements.

Documentation has been added to the relevant resource pages.

I have tested the ability to create a security group egress route to a prefix list and confirmed the behaviour in the AWS web console.

As discussed in GH-3413, I did not create a new resource for a prefix list since these are objects internally managed by AWS, i.e. there is no associated resource lifetime to manage.

[dtolnay]

I rebased again to fix a conflict with #7164.

[catsby]

Hey all – I added to the tests with a lookup and check on the Prefix ID in #7511, we'll go with that one.

Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.