### 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_
from datetime import datetime
from functools import lru_cache
from typing import Any, Dict, Tuple
from urllib.parse import urlsplit
import pytest
from botocore.awsrequest import AWSRequest, create_request_object
from botocore.config import Config
from botocore.model import OperationModel, ServiceModel, Shape, StructureShape
from localstack.aws.protocol.service_router import determine_aws_service_name, get_service_catalog
from localstack.http import Request
from localstack.utils.aws import aws_stack
from localstack.utils.run import to_str
def _collect_operations() -> Tuple[ServiceModel, OperationModel]: