### 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_
query_candidates = [
            service
            for service in services.by_operation(values["Action"])
            if services.get(service).protocol in ("ec2", "query")
        ]
        if len(query_candidates) == 1:
            return query_candidates[0]
        if "Version" in values:
            for service in list(query_candidates):
                service_model = services.get(service)
                if values["Version"] != service_model.api_version:
                    
                    query_candidates.remove(service)
        if len(query_candidates) == 1:
            return query_candidates[0]
        candidates.update(query_candidates)
    
    resolved_conflict = resolve_conflicts(candidates, request)
    if resolved_conflict:
        return resolved_conflict
    
    legacy_match = legacy_rules(request)
    if legacy_match:
        return legacy_match
    if signing_name:
        return signing_name
    if candidates:
        return candidates.pop()
    return None