Security Group resource fails to destroy when a rule references another group or entity that does not exist

[overlordchin]

parent ticket: #19932

Problem statement. When a security resource references a resource that does not exist - more specifically if a rule uses a second security group as a source to allow traffic from and that group no longer exists (has been destroyed outside of terraform), a terraform destroy will fail with one of the following errors:

Error: No security group with ID "sg-0c9450f52f3c5e7dc"
Error: Error deleting security group: DependencyViolation: resource sg-02cd8eca8d630233c has a dependent object status 400

Expected behavior - A warning is displayed and the destroy continues to remove the resource as normal.

[github-actions]

This functionality has been released in v4.29.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.