### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

When re-subscribing an SQS queue to an SNS topic with the attribute "RawMessageDelivery=true", localstack throws an error.
It's occuring both on my AWS Java Client and with CLI awslocal
it's working well without this attribute


### Expected Behavior

Since the queue is subscribed with the attribute "RawMessageDelivery=true" to the topic already, it should be a no-op and simply return the same subscription arn.



### How are you starting LocalStack?

With a docker-compose file

### Steps To Reproduce

#### How are you starting localstack (e.g., `bin/localstack` command, arguments, or `docker-compose.yml`)

    docker run localstack/localstack

#### Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

```
awslocal sns create-topic --name localstack-topic
awslocal sqs create-queue --queue-name localstack-queue

awslocal sns subscribe   --topic-arn arn:aws:sns:eu-central-1:000000000000:localstack-topic    --protocol sqs    --notification-endpoint arn:aws:sqs:eu-central-1:000000000000:localstack-queue    --return-subscription-arn  --attributes RawMessageDelivery=True

awslocal sns subscribe   --topic-arn arn:aws:sns:eu-central-1:000000000000:localstack-topic    --protocol sqs    --notification-endpoint arn:aws:sqs:eu-central-1:000000000000:localstack-queue    --return-subscription-arn  --attributes RawMessageDelivery=True
```

### Environment

```markdown
aws-cli/1.22.34 Python/3.10.12 Linux/6.2.0-32-generic botocore/1.31.47
```


### Anything else?

subscription created with "RawMessageDelivery=true"

![image](https://github.com/localstack/localstack/assets/98832464/faac719d-b5fe-4920-a756-28abc17fd0e7)


but if the subscription is created without attributes it's working well 

![image](https://github.com/localstack/localstack/assets/98832464/44ed7afd-a3b2-4a19-aff4-cba7b75ad52c)


maybe it's related to https://github.com/localstack/localstack/issues/9058
"Message": message,
            },
        )
        json_response = xmltodict.parse(response.content)
        json_response["Response"].pop("@xmlns")
        json_response["Response"]["ResponseMetadata"][
            "HTTPStatusCode"
        ] = response.status_code
        json_response["Response"]["ResponseMetadata"]["HTTPHeaders"] = dict(response.headers)
        snapshot.match("post-request", json_response)
        assert response.status_code == 200
        assert b"<Response" in response.content
        rs = aws_client.sqs.receive_message(
            QueueUrl=queue_url, VisibilityTimeout=0, WaitTimeSeconds=5
        )
        snapshot.match("messages", rs)
        msg_body = json.loads(rs["Messages"][0]["Body"])
        assert msg_body["TopicArn"] == topic_arn
        assert msg_body["Message"] == message
    @markers.aws.validated
    def test_publish_wrong_arn_format(self, snapshot, aws_client):
        message = "Good news everyone!"
        with pytest.raises(ClientError) as e:
            aws_client.sns.publish(Message=message, TopicArn="randomstring")
        snapshot.match("invalid-topic-arn", e.value.response)
        with pytest.raises(ClientError) as e:
            aws_client.sns.publish(Message=message, TopicArn="randomstring:1")
        snapshot.match("invalid-topic-arn-1", e.value.response)
    @markers.aws.validated
    def test_publish_message_by_target_arn(