### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

When passed to SQS, keys of the messages attributes on SNS are renamed from StringValue to Value and DataType to Type.

### Expected Behavior

The keys should not be renamed

### 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

#### Flow
 - Create a SQS Queue
 - Create a SNS Topic
 - Configure a Subscription of the new Topic that sends to the SQS queue (specify a raw delivery at true)
 - Publish a message to SNS Topic with attribute { DataType: "string", StringValue: "anything"}
 - Attributes are no more StringValue but just value. 

(can't provide more, I have issues with my awslocal, I got this issue with the PHP client initially)

### Environment

```markdown
- OS: Docker Desktop for mac
- LocalStack: 1.4
```


### Anything else?

The AWS SNS official documentation : https://docs.aws.amazon.com/sns/latest/api/API_MessageAttributeValue.html


MR for fix is coming
snapshot.match("messages-no-filter-after-publish-ok-1", response_after_publish_no_filter)
        response_after_publish_filter = aws_client.sqs.receive_message(
            QueueUrl=queue_url_with_filter, VisibilityTimeout=0, WaitTimeSeconds=sqs_wait_time
        )
        # t
        snapshot.match("messages-with-filter-after-publish-filtered", response_after_publish_filter)
    @pytest.mark.aws_validated
    @pytest.mark.skip_snapshot_verify(
        paths=["$.invalid-token.Error.Message"]  # v
    )
    def test_sns_confirm_subscription_wrong_token(self, sns_create_topic, snapshot, aws_client):
        topic_arn = sns_create_topic()["TopicArn"]
        with pytest.raises(ClientError) as e:
            wrong_topic = topic_arn[:-1] + "i"
            aws_client.sns.confirm_subscription(
                TopicArn=wrong_topic,
                Token="51b2ff3edb475b7d91550e0ab6edf0c1de2a34e6ebaf6c2262a001bcb7e051c43aa00022ceecce70bd2a67b2042da8d8eb47fef7a4e4e942d23e7fa56146b9ee35da040b4b8af564cc4184a7391c834cb75d75c22981f776ad1ce8805e9bab29da2329985337bb8095627907b46c8577c8440556b6f86582a954758026f41fc62041c4b3f67b0f5921232b5dae5aaca1",
            )
        snapshot.match("topic-not-exists", e.value.response)
        with pytest.raises(ClientError) as e:
            aws_client.sns.confirm_subscription(TopicArn=topic_arn, Token="randomtoken")
        snapshot.match("invalid-token", e.value.response)
        with pytest.raises(ClientError) as e:
            aws_client.sns.confirm_subscription(
                TopicArn=topic_arn,
                Token="51b2ff3edb475b7d91550e0ab6edf0c1de2a34e6ebaf6c2262a001bcb7e051c43aa00022ceecce70bd2a67b2042da8d8eb47fef7a4e4e942d23e7fa56146b9ee35da040b4b8af564cc4184a7391c834cb75d75c22981f776ad1ce8805e9bab29da2329985337bb8095627907b46c8577c8440556b6f86582a954758026f41fc62041c4b3f67b0f5921232b5dae5aaca1",
            )
        snapshot.match("token-not-exists", e.value.response)
@pytest.mark.only_localstack
class TestSNSMultiAccounts: