Terraform deprecation warning for usage of lifecycle_rule

[achave11-ucsc]

$ CI_COMMIT_REF_NAME=develop make -C terraform/browser plan

...

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
╷
│ Warning: Argument is deprecated
│
│   with aws_s3_bucket.browser,
│   on browser.tf.json line 62, in resource[0].aws_s3_bucket[0].browser:
│   62:                         "lifecycle_rule": {
│   63:                             "id": "azul-dummy-dev",
│   64:                             "enabled": false,
│   65:                             "expiration": {
│   66:                                 "days": 36500
│   67:                             }
│   68:                         },
│
│ Use the aws_s3_bucket_lifecycle_configuration resource instead
│
│ (and 3 more similar warnings elsewhere)

$ CI_COMMIT_REF_NAME=develop make -C terraform/shared plan

...

Plan: 0 to add, 3 to change, 1 to destroy.
╷
│ Warning: Argument is deprecated
│
│   with aws_s3_bucket.trail,
│   on shared.tf.json line 95, in resource[3].aws_s3_bucket[0].trail:
│   95:                         "lifecycle_rule": {
│   96:                             "id": "azul-dummy-dev",
│   97:                             "enabled": false,
│   98:                             "expiration": {
│   99:                                 "days": 36500
│  100:                             }
│  101:                         },
│
│ Use the aws_s3_bucket_lifecycle_configuration resource instead
│
│ (and 3 more similar warnings elsewhere)
╵

[dsotirho-ucsc]

Spike to reproduce without -compact-warnings and update description.

[hannes-ucsc]

We created (2c7ada2) these dummy lifecycle rules specificaly to ensure that no other rules exist on the bucket.

I'm doubtful that TF will go forward with the deprecation since there is a valid use case for both methods of specifying a lifecycle rule. The inline method assumes full control, the non-inline method allows for lifecycle rules not controlled by TF.

If TF does in fact remove the inline method, we can easily drop the dummies.