### 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_
},
    "es": {
        "/2015-01-01": "es",
        "/2021-01-01": "opensearch",
    },
    "sagemaker": {
        "/endpoints": "sagemaker-runtime",
        "/human-loops": "sagemaker-a2i-runtime",
    },
}
def custom_signing_name_rules(signing_name: str, path: str) -> Optional[str]:
    """
    Rules which are based on the signing name (in the auth header) and the request path.
    """
    rules = signing_name_path_prefix_rules.get(signing_name)
    if not rules:
        if signing_name == "servicecatalog":
            if path == "/":
                
                return "servicecatalog"
            else:
                
                return "servicecatalog-appregistry"
        return
    for prefix, name in rules.items():
        if path.startswith(prefix):
            return name
    return rules.get("*", signing_name)
def custom_host_addressing_rules(host: str) -> Optional[str]:
    """