### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

I created an S3 bucket with the name `pictures`. Each time I tried to write to it, I would get a CORS error. 

I used the same code as I used for another bucket which was working fine (`originaluploads`). I even verified that the same code path that was causing issues under `pictures` worked fine when pointed against the `originaluploads` bucket. 

When I renamed the `pictures` bucket to `userpictures`, the code worked fine. 

Is `pictures` a reserved bucket name in LocalStack? If so, I couldn't find any documentation. Otherwise, seems like a bug. 

### Expected Behavior

`pictures`-named S3 buckets shouldn't reject with CORS errors.

### How are you starting LocalStack?

With a docker-compose file

### Steps To Reproduce

Attempt to write to an S3 bucket named `pictures`.

### Environment

```markdown
- OS: Docker
- LocalStack: 2.0.0
```


### Anything else?

_No response_
service: ServiceModel, operation: OperationModel, caplog
):
    caplog.set_level("CRITICAL", "botocore")
    
    client = _client(service.service_name)
    request_context = {
        "client_region": client.meta.region_name,
        "client_config": client.meta.config,
        "has_streaming_input": operation.has_streaming_input,
        "auth_type": operation.auth_type,
    }
    request_args = _create_dummy_request_args(operation)
    
    request_dict = client._convert_to_request_dict(
        request_args, operation, "http://localhost.localstack.cloud", request_context
    )
    request_object = create_request_object(request_dict)
    client._request_signer.sign(operation.name, request_object)
    request: Request = _botocore_request_to_localstack_request(request_object)
    
    detected_service_name = determine_aws_service_name(request)
    
    assert service.service_name == detected_service_name
def test_endpoint_prefix_based_routing():