### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

```
$ docker run -d -p 4566:4566 localstack/localstack:2.3

$ aws --no-sign-request --endpoint-url=http://localhost:4566 s3 mb s3://tustvold
make_bucket: tustvold
```

If we then create a path with a percent encoded object path, deleting it works correctly
 
```
$ curl -X PUT --data-binary 'test' -H "Content-Type: text/plain" 'http://localhost:4566/tustvold/a%252Fb.txt'

$ aws --no-sign-request --endpoint-url=http://localhost:4566 s3 ls s3://tustvold
2023-10-21 21:33:50          4 a%2Fb.txt

$ aws s3api delete-objects --no-sign-request --endpoint http://localhost:4566 --bucket tustvold --delete 'Objects=[{Key=a%2Fb.txt}]'
{
    "Deleted": [
        {
            "Key": "a%2Fb.txt"
        }
    ]
}
```

However, if the object key is a percent encoded emoji, we get very peculiar behaviour, where the DeleteObject appears to be trying to delete the percent decoded version of the object

```
$ aws --no-sign-request --endpoint-url=http://localhost:4566 s3 ls s3://tustvold
$ curl -X PUT --data-binary 'test' -H "Content-Type: text/plain" 'http://localhost:4566/tustvold/a/%25F0%259F%2598%2580.file'

$ aws --no-sign-request --endpoint-url=http://localhost:4566 s3 ls s3://tustvold --recursive
2023-10-21 21:36:07          4 a/%F0%9F%98%80.file

$ aws s3api delete-objects --no-sign-request --endpoint http://localhost:4566 --bucket tustvold --delete 'Objects=[{Key=a/%F0%9F%98%80.file}]'
{
    "Deleted": [
        {
            "Key": "a/😀.file"
        }
    ]
}
$ aws --no-sign-request --endpoint-url=http://localhost:4566 s3 ls s3://tustvold --recursive
2023-10-21 21:36:07          4 a/%F0%9F%98%80.file
```

### Expected Behavior

In version 2.0 this worked correctly

```
$ docker run -d -p 4566:4566 localstack/localstack:2.0

$ aws --no-sign-request --endpoint-url=http://localhost:4566 s3 mb s3://tustvold

$ curl -X PUT --data-binary 'test' -H "Content-Type: text/plain" 'http://localhost:4566/tustvold/a/%25F0%259F%2598%2580.file'

$ aws s3api delete-objects --no-sign-request --endpoint http://localhost:4566 --bucket tustvold --delete 'Objects=[{Key=a/%F0%9F%98%80.file}]'
{
    "Deleted": [
        {
            "Key": "a/%F0%9F%98%80.file"
        }
    ]
}

$ aws --no-sign-request --endpoint-url=http://localhost:4566 s3 ls s3://tustvold --recursive
```

### How are you starting LocalStack?

With a docker-compose file

### Steps To Reproduce

See above

### Environment

```markdown
- OS:
- LocalStack:
```


### Anything else?

_No response_
assert response["Contents"][0]["Size"] == 9
        snapshot.match("list_s", response)
        snapshot.match("list_s_headers", response["ResponseMetadata"]["HTTPHeaders"])
        # will 
        response_vhost = .get(_bucket_url_vhost(bucket_name).replace("https://", "http://"))
        content_vhost = response_vhost.content.decode("utf-8")
        assert "<Key>my-content</Key>" in content_vhost
        # TODO 
        # asse
        assert "<Size>9</Size>" in content_vhost
        snapshot.match("request_vhost_url_content", content_vhost)
        # TODO 
        snapshot.match("request_vhost_headers", dict(response_vhost.headers))
        response_path_s = .get(_bucket_url(bucket_name))
        content_path_s = response_path_s.content.decode("utf-8")
        assert "<Key>my-content</Key>" in content_path_s
        # TODO 
        # asse
        assert "<Size>9</Size>" in content_path_s
        snapshot.match("request_path_url_content", content_path_s)
        snapshot.match("request_path_headers", dict(response_path_s.headers))
        assert content_vhost == content_path_s
    @markers.aws.validated
    @markers.snapshot.skip_snapshot_verify(
        condition=lambda: not is_native_provider(), paths=["$..ServerSideEncryption", "$..Prefix"]
    )
    @markers.snapshot.skip_snapshot_verify(
        condition=is_old_provider, paths=["$..ContentLanguage", "$..VersionId"]
    )
    def test_s3_put_more_than_1000_items(self, s3_bucket, snapshot, aws_client):