### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

Im using AWS SDK v3
We use the `GetTopicAttributesCommand` to validate topic existence (there is not other way to do it), then we check the error code and error message.

When trying to get attributes of a topic by ARN with lockstack, it returns error with different error message than AWS:

```ts
{
    Code: 'NotFound',
    Message: 'Topic with arn <MY ARN> not found',
    message: 'Topic with arn <MY ARN> not found'
  }
```

The original AWS error

```ts
{
  Type: "Sender",
  Code: "NotFound",
  Message: "Topic does not exist",
  message: "Topic does not exist"
}
```

### Expected Behavior

Lockstack should return exact same error structure as AWS cloud


```ts
{
  Type: "Sender",
  Code: "NotFound",
  Message: "Topic does not exist",
  message: "Topic does not exist"
}
```

### How are you starting LocalStack?

With the `localstack` script

### Steps To Reproduce

```ts
  const client = new SNSClient({ })
  try {
    await client.send(new GetTopicAttributesCommand({ TopicArn: '<ARN TO TEST>' }))
  } catch (err) {
    console.log(err)
  }
  ```
  
  Run this both with AWS and lockstack and u will see the diff


### Environment

```markdown
- OS: osX
- LocalStack:latest
```


### Anything else?

_No response_
import contextlib
import json
import logging
import queue
import random
import time
from io import BytesIO
from operator import itemgetter
import pytest
import requests
import xmltodict
from botocore.exceptions import ClientError
from pytest_httpserver import HTTPServer
from werkzeug import Response
from localstack import config
from localstack.aws.accounts import get_aws_account_id
from localstack.aws.api.lambda_ import Runtime