### 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_
return "lambda"
    
    if path.startswith("/shell") or path.startswith("/dynamodb/shell"):
        return "dynamodb"
    
    
    if path == "/health" or path.startswith("/_localstack") or path.startswith("/_pods"):
        return None
    
    
    stripped = path.strip("/")
    if method in ["GET", "HEAD"] and stripped:
        
        return "s3"
    
    if stripped and "/" not in stripped:
        if method == "PUT":
            
            return "s3"
        if method == "POST" and "key" in request.values:
            
            return "s3"
    
    if "aws-cli/" in str(request.user_agent):
        return "s3"
    
    values = request.values
    if any(
        value in values
        for value in [