s3 bucket notification configuration resource cannot be destroyed if the bucket no longer exists

[overlordchin]

parent ticket: #19932

Problem statement. When an aws_s3_bucket_notification resource references a bucket that no longer exists(has been destroyed outside of terraform), a terraform destroy will fail with one of the following errors:

Error: error deleting S3 Bucket Notification Configuration NoSuchBucket: The specified bucket does not exist

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

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. 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.