### 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_
"""
    Encapsulates the different fields that might indicate which service a request is targeting.
    This class does _not_ contain any data which is parsed from the body of the request in order to defer or even avoid
    processing the body.
    """
    
    
    signing_name: Optional[str] = None
    
    target_prefix: Optional[str] = None
    
    operation: Optional[str] = None
    
    host: Optional[str] = None
    
    path: Optional[str] = None
def _extract_service_indicators(request: Request) -> _ServiceIndicators: