### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

Given the following minimal terraform code that creates two s3 buckets where one of the buckets is used for logging

```tf
terraform {
  required_version = ">= 1.5.2"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.8.0"
    }
  }
}

resource "aws_s3_bucket" "bucket" {
  bucket = "main"
}

resource "aws_s3_bucket" "logging" {
  bucket = "logging"
}

resource "aws_s3_bucket_logging" "bucket" {
  bucket = aws_s3_bucket.bucket.id

  target_bucket = aws_s3_bucket.logging.id
  target_prefix = "log/"
}
```

Using `tflocal` to `tflocal apply` the resources to localstack running in docker-compose works as expected but `tflocal destroy` will become stuck at 
```
aws_s3_bucket_logging.bucket: Destroying... [id=main]
aws_s3_bucket_logging.bucket: Still destroying... [id=main, 10s elapsed]
```

when reviewing the localstack output the following error is observed repeatedly

```
localstack_main | 2023-08-03T00:01:55.897  INFO --- [   asgi_gw_2] localstack.request.aws     : AWS s3.PutBucketLogging => 500 (InternalError)
localstack_main | 2023-08-03T00:01:55.899  INFO --- [   asgi_gw_1] localstack.request.http    : PUT / => 500
localstack_main | 2023-08-03T00:01:55.949 ERROR --- [   asgi_gw_2] l.aws.handlers.logging     : exception during call chain: 'NoneType' object has no attribute 'get'
```

### Expected Behavior

`tflocal destroy` to destroy the `aws_s3_bucket_logging` logging resource.  Using terraform instead of tflocal with the same terraform configuration succeeds during apply and destroy

### How are you starting LocalStack?

With a docker-compose file

### Steps To Reproduce

1. Create a minimal terraform module with a `main.tf` that includes the terraform code above
2. from the terraform module execute `tflocal init`
3. from the terraform module execute `tflocal apply`
4. observe the resources are created in localstack
5. from the terraform module execute `tflocal destroy`
6. observe the 500 error in the localstack logs and the terraform output is stuck on "Still destroying..."


### Environment

```markdown
- OS: macOS 13.4.1
- LocalStack: latest
```


### Anything else?

_No response_
self, s3_bucket, domain, use_virtual_address, aws_client
    ):
        """Assert that /favicon.ico s can be created/accessed/deleted using amazonaws host headers"""
        s3_key = "favicon.ico"
        content = b"test 123"
        aws_client.s3.put_(Bucket=s3_bucket, Key=s3_key, Body=content)
        aws_client.s3.head_(Bucket=s3_bucket, Key=s3_key)
        path = s3_key if use_virtual_address else f"{s3_bucket}/{s3_key}"
        url = f"{config.get_edge_url()}/{path}"
        headers = aws_stack.mock_aws_request_headers("s3")
        headers["host"] = f"{s3_bucket}.{domain}" if use_virtual_address else domain
        # get 
        result = .get(url, headers=headers)
        assert result.ok
        assert result.content == content
        # dele
        result = .delete(url, headers=headers)
        assert result.ok
        # asse
        with pytest.raises(ClientError) as exc:
            aws_client.s3.head_(Bucket=s3_bucket, Key=s3_key)
        assert exc.value.response["Error"]["Message"] == "Not Found"
class TestS3BucketPolicies:
    def test_access_to_bucket_not_denied(self, s3_bucket, monkeypatch, aws_client):