refactor: use assume_role block for role_arn

[d3adb5]

Use the assume_role.role_arn property instead of the now deprecated role_arn. This should also fix potential issues with the AWS provider trying to assume a nonexistent role.

what

• Moved role_arn in the generated backend configuration into the assume_role
  block.

why

• The role_arn configuration property is now deprecated in favor of the
  assumeassume_role block. This change deals with the issued warning and with
  potential issues involving the Terraform AWS provider being unable to assume a
  role that doesn't exist.

references

• Terraform AWS Provider v4.67.0 documentation

[d3adb5]

Not too sure what to make of the issues pointed out in the Checkov status check: I do see them showing up in a scan with tfsec, but fixing them is unfortunately out of the scope of this pull request, in my opinion.

Let me know how you guys wish to address that.

[martingaleano]

Not too sure what to make of the issues pointed out in the Checkov status check: I do see them showing up in a scan with tfsec, but fixing them is unfortunately out of the scope of this pull request, in my opinion.

Let me know how you guys wish to address that.

I don't know if there is a specific reason to create the replication bucket with this set up, but maybe for future issues, we can add a comment inside resource block in order to skip the checkov validation (Ref: https://www.checkov.io/2.Basics/Suppressing%20and%20Skipping%20Policies.html)