Reorder S3 bucket ACL enum values for consistency

[Copilot]

The ACL enum values in aws_s3_bucket_invalid_acl.go were ordered inconsistently compared to standard conventions and similar code in the repository.

Changes:

• Reordered enum list to: private, public-read, public-read-write, authenticated-read, aws-exec-read, bucket-owner-read, bucket-owner-full-control, log-delivery-write
• Groups common ACLs first, authentication ACLs alphabetically, owner ACLs, then bucket-specific ACL
• All 8 valid ACL values unchanged, only order modified

enum: []string{
    "private",
    "public-read",
    "public-read-write",
    "authenticated-read",      // moved before aws-exec-read
    "aws-exec-read",
    "bucket-owner-read",
    "bucket-owner-full-control",
    "log-delivery-write",      // moved to end as bucket-specific
}

Original prompt

Please update enum list in rules/aws_s3_bucket_invalid_acl.go

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.