feat: Add bucket versioning status as an output

[kunickiaj]

Description

When creating replicated buckets, expose a versioning status output in order to be able to create a dependency on replica buckets being ready (versioning enabled). Otherwise applying replication rules targeting a bucket which isn't fully set up may fail.

Motivation and Context

There is no data source for bucket versioning status or exposed attributes for versioning except the aws_s3_bucket_versioning resource which is currently encapsulated by this module.

Take the following (abbreviated) example:

module "bucket" {
  source  = "terraform-aws-modules/s3-bucket/aws"
  version = "5.2.0"

  bucket = "my-bucket"

  replication_configuration = {
    ....
  }
  
  versioning = {
    enabled = true
  }
}

module "replica_bucket" {
  source  = "terraform-aws-modules/s3-bucket/aws"
  version = "5.2.0"

  bucket = "my-bucket-replica"

  versioning = {
    enabled = true
  }
}

This may result in:

Error: creating S3 Bucket (my-bucket) Replication Configuration: operation error S3: PutBucketReplication, https response error StatusCode: 400, RequestID: xxxx, HostID: xxxxx, api error InvalidRequest: Destination bucket must have versioning enabled.

The hope is that by depending on the versioning resource could delay replication rule creation until the destination bucket is ready (and has versioning configuration fully applied).

Breaking Changes

No breaking changes

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[antonbabenko]

LGTM

[antonbabenko]

@kunickiaj Please fix the failing CI before the merge.

[kunickiaj]

@kunickiaj Please fix the failing CI before the merge.

manually updated to match, i think. might be some version mismatch. locally terraform-docs is outputting a different order.

[antonbabenko]

@kunickiaj Something is not right there still.

[kunickiaj]

fairly certain this should be correct

[antonbabenko]

This PR is included in version 5.3.0 🎉

[github-actions]

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.