remove skip_requesting_account_id from TF files following S3 changes

[bentsku]

We got several reports that the skip_requesting_account_id flag in Terraform now breaks the deployment: the S3 Bucket resource (aws_s3_bucket) is now using the S3 Control service to manage its tags, and it needs a properly formed account id to be able to form its endpoint.

If the flag is set, it returns the following error:

│ Error: listing tags for S3 (Simple Storage) Bucket (my-bucket-ritesh): operation error S3 Control: ListTagsForResource, failed to resolve service endpoint, endpoint rule error, AccountId must only contain a-z, A-Z, 0-9 and `-`.
│   with aws_s3_bucket.test-bucket,
│   on provider.tf line 37, in resource "aws_s3_bucket" "test-bucket":
│   37: resource "aws_s3_bucket" "test-bucket" {
│

This PR removes mentions from this config flag from our samples, to avoid users being greeted by an error.

See:

• https://stackoverflow.com/questions/79848271/localstack-terraform-s3-creation-error-of-error-listing-tags-for-s3-simple-sto
• bug: S3 CreateBucket fails with MalformedXML after upgrading Terraform AWS provider to v6.23 localstack#13426 (comment)

[quetzalliwrites]

tyvm for your contribution @bentsku 🙇🏻